eth_blockNumber on Linea
Everything below was measured on 2026-10-13 by calling eth_blockNumber on Linea 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 Linea: what we measured
| Head block when measured | 32,311,939 (0x1ed0a83) |
|---|---|
| Age of that block when read | 17 s |
| Average block time (last 1,000 blocks) | 14 s |
| Median gap between newHeads over WebSocket | 7.8 s |
| "safe" behind the head | 1,141 blocks (about 4.3 hours) |
| "finalized" behind the head | 0 blocks |
What this means for polling
With 14 s blocks, polling more often than every 14 seconds mostly returns the same number and spends requests for nothing. viem's default polling interval of 4 seconds is already shorter than one block on Linea.
"finalized" pointed at the head block itself on Linea: 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 Linea's own finality rules rather than the tag.
Compared with other chains
Measured by the gap between WebSocket headers, Linea has the 38th fastest block cadence of the 40 chains we measure.
Example request
curl -s https://rpc.swiftnodes.io/rpc/linea?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/linea?key=YOUR_API_KEY"),
});
const head = await client.getBlockNumber(); // bigint
// Follow the chain: poll about once per block (14 s on Linea)
const unwatch = client.watchBlockNumber({
pollingInterval: 13656,
onBlockNumber: (n) => console.log("new head", n),
});Other methods on Linea
- eth_chainIdSupported
- eth_getBalanceSupported
- eth_getBlockByNumberSupported
- eth_getTransactionByHashSupported
- eth_getTransactionReceiptSupported
- eth_callSupported
- eth_estimateGasSupported
- eth_gasPriceSupported
- eth_maxPriorityFeePerGasSupported
- eth_sendRawTransactionSupported
- eth_getTransactionCountSupported
- eth_getCodeSupported
- eth_subscribeSupported
- eth_getLogsSupported
- eth_getBlockReceiptsSupported
- eth_feeHistorySupported
- eth_getProofSupported
- eth_createAccessListSupported
- debug_traceCallSupported
- trace_blockSupported
- trace_transactionSupported
eth_blockNumber on other chains
- Ethereum
- Base
- Arbitrum
- Optimism
- Polygon
- BNB Smart Chain
- Avalanche
- Sonic
- 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
- Story
- 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 Linea support eth_blockNumber?
Yes. eth_blockNumber answered on the SwiftNodes Linea endpoint when our weekly probe called it through the customer path (2026-10-13).
How fast are blocks on Linea?
About 14 s per block, averaged over recent blocks (measured 2026-10-13).
How often should I poll eth_blockNumber on Linea?
About once per block, every 14 s. Faster polling mostly returns the same number.
Linea endpoints, live block height and WebSocket status are on the Linea RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.