eth_blockNumber on Ethereum Classic
Everything below was measured on 2026-10-13 by calling eth_blockNumber on Ethereum Classic 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 Ethereum Classic: what we measured
| Head block when measured | 25,527,642 (0x185855a) |
|---|---|
| Age of that block when read | 25 s |
| Average block time (last 1,000 blocks) | 12 s |
| "safe" behind the head | not available (safe block not found) |
| "finalized" behind the head | not available (finalized block not found) |
What this means for polling
With 12 s blocks, polling more often than every 12 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 Ethereum Classic.
Example request
curl -s https://rpc.swiftnodes.io/rpc/etc?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/etc?key=YOUR_API_KEY"),
});
const head = await client.getBlockNumber(); // bigint
// Follow the chain: poll about once per block (12 s on Ethereum Classic)
const unwatch = client.watchBlockNumber({
pollingInterval: 12356,
onBlockNumber: (n) => console.log("new head", n),
});Other methods on Ethereum Classic
- 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_subscribeNot available
- 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
- 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
- Story
- Soneium
- Sei
- Hyperliquid
- Taiko
- Morph
- Ink
- Katana
- opBNB
- Mode
- Flare
- Core
- Chiliz
- Telos EVM
- Tempo
- Cronos
- Manta Pacific
- Shibarium
- Boba Network
- Arbitrum Nova
- Immutable zkEVM
Frequently asked questions
Does Ethereum Classic support eth_blockNumber?
Yes. eth_blockNumber answered on the SwiftNodes Ethereum Classic endpoint when our weekly probe called it through the customer path (2026-10-13).
How fast are blocks on Ethereum Classic?
About 12 s per block, averaged over recent blocks (measured 2026-10-13).
How often should I poll eth_blockNumber on Ethereum Classic?
About once per block, every 12 s. Faster polling mostly returns the same number.
Ethereum Classic endpoints, live block height and WebSocket status are on the Ethereum Classic RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.