eth_getBlockByNumber on BOB
Everything below was measured on 2026-10-13 by calling eth_getBlockByNumber on BOB through the same endpoint customers use, and is re-measured weekly.
What eth_getBlockByNumber does
Returns a block by number or tag (latest, safe, finalized, pending, earliest): the header, and either the transaction hashes or the full transactions. Indexers, explorers and wallets use it to follow the chain.
eth_getBlockByNumber on BOB: what we measured
| Header fields | 26 |
|---|---|
| Transactions per block | 1, 1 in five consecutive blocks |
| Response size, full transactions (true) | 2.7 KB average |
| Response size, hashes only (false) | 1.8 KB |
| Gas limit | 30,000,000 |
| Gas used in the latest block | 46,302 (0.154% of the limit) |
| Base fee | 252 wei |
| Tag "safe" | block 39,516,968 |
| Tag "finalized" | block 39,515,198 |
| Tag "pending" | block 39,517,211 |
| Tag "earliest" | block 0 |
What is different on BOB
The header includes the fields added by London (EIP-1559 base fee), Shanghai (withdrawals), Cancun (EIP-4844 blob gas), Cancun (EIP-4788 beacon root), Prague (EIP-7685 requests). Code that assumes Ethereum's current header shape will parse it as is.
2 of the 2 transactions in those five blocks were system transactions (2 × type 0x7e, L1-to-L2 deposit (OP Stack)). They are not user activity: filter them out when counting transactions.
"finalized" was 2,011 blocks (about 67 min) behind the head.
A real BOB block header
From block 39,517,205, as our endpoint returned it (long hex values shortened).
{
"baseFeePerGas": "0xfc",
"blobGasUsed": "0x0",
"difficulty": "0x0",
"excessBlobGas": "0x0",
"extraData": "0x01000000fa000000060000000000000000",
"gasLimit": "0x1c9c380",
"gasUsed": "0xb4de",
"hash": "0xb4348a97255f77ea0b21bad2a4dde7878eb6f76b745437c842edcfd7ad1bc1f1",
"logsBloom": "0x0000000000000000…(256 bytes)",
"miner": "0x4200000000000000000000000000000000000011",
"mixHash": "0x19b6c56b461b6986fed2fa0c1276a7a2ed5e155fdb8f6dc41c916cbcf25d46da",
"nonce": "0x0000000000000000",
"number": "0x25afc15",
"parentBeaconBlockRoot": "0x23ccee0c1430745e5f06a53fcfb5554b7a6ead8a34ed1ee846d0a3b9565b4515",
"parentHash": "0xd2829f2299a04ea1689b491cbf184e64c3e2d3b4bd9c84b8bc14c78b15dbfb60",
"receiptsRoot": "0x1dffacd88ca66af8d6519079ebb539ee1bac1cc1f36a8e8288de34d66a53d335",
"requestsHash": "0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
"sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
"size": "0x38b",
"stateRoot": "0x36456a7441589e53a10d44bf223d5635423bb133740839a5e896f51282727b38",
"timestamp": "0x6ace2b4d",
"transactions": "1 transactions",
"transactionsRoot": "0x5f29906077e86790aec714d91b36b70c0f18e62bda31d1a877119330e24fd09c",
"uncles": [],
"withdrawals": [],
"withdrawalsRoot": "0xcedc3d82a45efdf293c5f2654433146064d96b72710b13fd10f66cbbb2304c6d"
}Example request
curl -s https://rpc.swiftnodes.io/rpc/bob?key=YOUR_API_KEY \
-X POST -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_getBlockByNumber","params":["latest",false]}'import { createPublicClient, http } from "viem";
const client = createPublicClient({
transport: http("https://rpc.swiftnodes.io/rpc/bob?key=YOUR_API_KEY"),
});
// Header plus transaction hashes (1.8 KB)
const block = await client.getBlock({ blockTag: "latest" });
// With full transactions (2.7 KB on average on BOB)
const full = await client.getBlock({ blockNumber: block.number, includeTransactions: true });
const userTxs = full.transactions.filter((t) => !["0x7e"].includes(t.typeHex));
// A block that will not be reorganised
const final = await client.getBlock({ blockTag: "finalized" });Other methods on BOB
- eth_blockNumberSupported
- eth_chainIdSupported
- eth_getBalanceSupported
- 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_transactionNot available
eth_getBlockByNumber 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
- 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 BOB support eth_getBlockByNumber?
Yes. eth_getBlockByNumber answered on the SwiftNodes BOB endpoint when our weekly probe called it through the customer path (2026-10-13).
How many transactions are in each BOB block?
In five consecutive blocks on 2026-10-13: 1, 1.
BOB endpoints, live block height and WebSocket status are on the BOB RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.