EVM

Arbitrum One

eth_getBlockByNumber

Pricing and latency over time for eth_getBlockByNumber on Arbitrum One, with Economy and Performance series. Below you’ll see daily provider lag (nodes in sync) and replay correctness for this method, plus related routes by usage.

Price over time

Economy vs Performance ($ per million requests)

Nodes in Sync (Lag Checks)

Daily in-sync status by provider for eth_getBlockByNumber on this chain.

10/19

10/21

10/23

10/25

10/27

10/29

Healthy (>=99%)

Warning (95-99%)

Degraded (50-95%)

Critical (<50%)

No data

Date	-
Provider	-
Lag check status	-

Node Correctness (Replay Checks)

Daily replay correctness by provider for eth_getBlockByNumber on this chain.

10/19

10/21

10/23

10/25

10/27

10/29

Healthy (>=99%)

Warning (95-99%)

Degraded (50-95%)

Critical (<50%)

No data

Date	-
Provider	-
Replay check status	-

Global latency

Caller-to-router p50 latency by region for this route (last 7 days).

Strategy

Region	Latency

Popular routes

Unichain eth_call

10,260,648 requests

41ms

Ethereum Mainnet eth_call

8,935,028 requests

21ms

BNB Smart Chain Mainnet eth_call

6,882,530 requests

20ms

eth_getBlockByNumber​