eth_blockNumber on Story
Everything below was measured on 2026-10-13 by calling eth_blockNumber on Story through the same endpoint customers use, and is re-measured weekly.
What eth_blockNumber does
Returns the number of the most recent block the node has, as a hex string. It is the cheapest way to tell whether a node is keeping up and the usual starting point for polling a chain.
eth_blockNumber on Story: what we measured
| Head block when measured | 23,300,079 (0x16387ef) |
|---|---|
| Age of that block when read | 6 s |
| Average block time (last 1,000 blocks) | 2.4 s |
| Median gap between newHeads over WebSocket | 2.2 s |
| "safe" behind the head | 0 blocks |
| "finalized" behind the head | 0 blocks |
What this means for polling
At 2.4 s per block, a one-second poll returns a new number on roughly one call in 2. Polling at the block time keeps you current without wasting requests.
"finalized" pointed at the head block itself on Story: its nodes report each new block as finalized, so the tag adds no safety over "latest". If you need settlement on Ethereum or protection from deep reorgs, check Story's own finality rules rather than the tag.
Compared with other chains
Measured by the gap between WebSocket headers, Story has the 34th fastest block cadence of the 40 chains we measure.
Example request
curl -s https://rpc.swiftnodes.io/rpc/story?key=YOUR_API_KEY \
-X POST -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'import { createPublicClient, http } from "viem";
const client = createPublicClient({
transport: http("https://rpc.swiftnodes.io/rpc/story?key=YOUR_API_KEY"),
});
const head = await client.getBlockNumber(); // bigint
// Follow the chain: poll about once per block (2.4 s on Story)
const unwatch = client.watchBlockNumber({
pollingInterval: 2363,
onBlockNumber: (n) => console.log("new head", n),
});Other methods on Story
- eth_chainIdSupported
- eth_getBalanceSupported
- eth_getBlockByNumberSupported
- eth_getTransactionByHashNot measured
- eth_getTransactionReceiptNot measured
- eth_callSupported
- eth_estimateGasSupported
- eth_gasPriceSupported
- eth_maxPriorityFeePerGasSupported
- eth_sendRawTransactionSupported
- eth_getTransactionCountNot measured
- eth_getCodeSupported
- eth_subscribeSupported
- eth_getLogsSupported
- eth_getBlockReceiptsSupported
- eth_feeHistorySupported
- eth_getProofSupported
- eth_createAccessListSupported
- debug_traceCallNot available
- trace_blockNot available
- trace_transactionNot available
eth_blockNumber on other chains
- Ethereum
- Base
- Arbitrum
- Optimism
- Polygon
- BNB Smart Chain
- Avalanche
- Sonic
- Linea
- Scroll
- zkSync Era
- Blast
- Mantle
- Gnosis
- Celo
- Berachain
- Monad
- Unichain
- Kaia
- PulseChain
- World Chain
- Ronin
- Abstract
- ApeChain
- MegaETH
- Fantom
- Lisk
- Hemi
- X Layer
- BOB
- Plasma
- Fraxtal
- Zora
- Soneium
- Sei
- Hyperliquid
- Taiko
- Morph
- Ink
- Katana
- Ethereum Classic
- opBNB
- Mode
- Flare
- Core
- Chiliz
- Telos EVM
- Tempo
- Cronos
- Manta Pacific
- Shibarium
- Boba Network
- Arbitrum Nova
- Immutable zkEVM
Frequently asked questions
Does Story support eth_blockNumber?
Yes. eth_blockNumber answered on the SwiftNodes Story endpoint when our weekly probe called it through the customer path (2026-10-13).
How fast are blocks on Story?
About 2.4 s per block, averaged over recent blocks (measured 2026-10-13).
How often should I poll eth_blockNumber on Story?
About once per block, every 2.4 s. Faster polling mostly returns the same number.
Story endpoints, live block height and WebSocket status are on the Story RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.