EVM Chain Block Times and RPC Limits, Measured

Published block times drift from reality: on the day we started measuring, 9 of the chain descriptions in our own catalogue were off by more than 2x (Cronos said 5–6 seconds and measured 0.42). This table is what the chains actually do, measured every week through a live RPC endpoint rather than copied from documentation.

Sorted fastest first. Each chain links to its page, where the same facts sit next to live status. Last measured 2026-09-23. Download: JSON.

ChainChain IDBlock timeFinalized tag lageth_getLogs rangeState depth (blocks)
Somnia5031100 msat head1,0001,000,000+
Robinhood Chain4663102 ms10,766 blocks (~18 min)50,000+1,000,000+
Arbitrum42161249 ms3,657 blocks (~15 min)5,0001,000,000+
opBNB204250 ms88 blocks (~22 s)50,000+64+
Monad143302 msat headunder 1,0001,000,000+
Cronos25396 msat head10,00064+
BNB Smart Chain56450 msat headunder 1,00064+
Sei1329453 msat head1,00010,000+
Telos EVM40500 msat head50,000+1,000,000+
Arc5042507 msat head5,00064+
Tempo4217561 msat headunder 1,00064+
Aurora1313161554625 msat head50,000+1,000,000+
0G16661904 msat head50,000+64+
Hyperliquid999983 msat head1,0001,000,000+
Celo422201 s1,443 blocks (~24 min)5,00064+
Unichain1301 s1,585 blocks (~26 min)5,00064+
Plasma97451 s1 block (~1 s)50,000+1,000,000+
Katana7474741 s1,194 blocks (~20 min)50,000+1,000,000+
Kaia82171 sat head50,000+1,000,000+
WEMIX11111 sat head50,000+1,000,000+
Ink570731 s1,201 blocks (~20 min)50,000+1,000,000+
Flare141.08 sat headunder 1,000under 64
Avalanche431141.16 s6 blocks (~7 s)50,000+64+
Sonic1461.29 sat head50,000+1,000,000+
Polygon1371.5 s3 blocks (~5 s)10,00064+
Base84532 s421 blocks (~14 min)5,00064+
Optimism102 s453 blocks (~15 min)under 1,0001,000,000+
Mantle50002 s632 blocks (~21 min)50,000+64+
Blast814572 s611 blocks (~20 min)50,000+64+
Berachain800942 sat head50,000+1,000,000+
Fraxtal2522 s765 blocks (~26 min)50,000+10,000+
Soneium18682 s647 blocks (~22 min)5,00064+
Mode344432 s904 blocks (~30 min)50,000+1,000,000+
Zora77777772 s1,279 blocks (~43 min)50,000+1,000,000+
Boba Network2882 s1,215 blocks (~41 min)5,0001,000,000+
Harmony16666000002.01 sno finalized tag1,0001,000,000+
Taiko1670002.03 s1,047 blocks (~35 min)50,000+1,000,000+
Story15142.13 sat head50,000+64+
IoTeX46892.5 sno finalized tag1,00064+
Chiliz888883 sno finalized tag50,000+64+
Core11163 s1 block (~3 s)50,000+64+
Tron (EVM)7281264283 s17 blocks (~51 s)5,000under 64
Polygon zkEVM11013.31 stag far behind head10,0001,000,000+
ZetaChain70003.77 sat head10,0001,000,000+
zkSync Era3243.96 stag far behind head50,000+10,000+
Scroll5343524.3 s1,183 blocks (~85 min)under 1,0001,000,000+
Fuse1225 sno finalized tag50,000+64+
Gnosis1005.08 s31 blocks (~3 min)5,00064+
Kava22225.73 sat head10,00064+
Linea591446.18 sat headunder 1,00064+
Shibarium1096.29 s22 blocks (~2 min)50,000+1,000,000+
Astar5926.5 s6 blocks (~39 s)1,0001,000,000+
peaq33386.54 s7 blocks (~46 s)50,000+64+
Manta Pacific16910 stag far behind head50,000+1,000,000+
PulseChain36911 s64 blocks (~11 min)50,000+64+
Beam433711 sat head1,0001,000,000+
Ethereum112 s67 blocks (~13 min)50,000+1,000,000+
Ethereum Classic6114 sno finalized tag50,000+64+
Metis108817 sno finalized tag50,000+1,000,000+
Syscoin573 min10 blocks (~26 min)50,000+64+
Arbitrum Nova421705 min1 block (~5 min)50,000+64+
HAQQ112357 minat head10,00064+

How it is measured

  • Block time: timestamp difference between the head and the block 1,000 below it, divided by 1,000. Chains that only produce blocks under load show long averages; that is what a poller experiences.
  • Finalized tag lag: how many blocks eth_getBlockByNumber("finalized") trails latest. “At head” means the latest block is already reported as finalized; lags over two hours are listed as “far behind” rather than as an exact figure.
  • eth_getLogs range: the largest of 1,000 / 5,000 / 10,000 / 50,000 blocks an address-filtered query was accepted for.
  • State depth: the deepest of 64 / 10,000 / 1,000,000 blocks back at which eth_getBalance still answers. 1,000,000+ is archive depth for practical purposes.

Limits are properties of the nodes serving a chain, not only of the chain, and can differ between the upstream nodes behind one endpoint. For which JSON-RPC methods each chain supports, see the method support matrix.