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