eth_getBlockByNumber on World Chain
Everything below was measured on 2026-10-13 by calling eth_getBlockByNumber on World Chain 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 World Chain: what we measured
| Header fields | 26 |
|---|---|
| Transactions per block | 13, 16, 16, 22, 22 in five consecutive blocks |
| Response size, full transactions (true) | 57.4 KB average |
| Response size, hashes only (false) | 2.6 KB |
| Gas limit | 280,000,000 |
| Gas used in the latest block | 3,169,400 (1.1% of the limit) |
| Base fee | 500,000 wei |
| Tag "safe" | block 36,280,769 |
| Tag "finalized" | block 36,280,177 |
| Tag "pending" | block 36,280,857 |
| Tag "earliest" | block 0 |
What is different on World Chain
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.
Asking for full transactions (second parameter true) made the response 21.9 times larger than hashes only. If you need only some transactions, fetch hashes and request those transactions or their receipts individually.
5 of the 89 transactions in those five blocks were system transactions (5 × type 0x7e, L1-to-L2 deposit (OP Stack)). They are not user activity: filter them out when counting transactions.
"finalized" was 679 blocks (about 23 min) behind the head.
A real World Chain block header
From block 36,280,851, as our endpoint returned it (long hex values shortened).
{
"hash": "0x695dcac567c8a7dd868d3d02ceb72caaa4dfd69d54eb5f8c98cf2679b98a5311",
"parentHash": "0x0efab5367874daaf8fab9c9cb821b803298052ecc1d1d32c5b5d4839528a6920",
"sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
"miner": "0x4200000000000000000000000000000000000011",
"stateRoot": "0x3cb25620f95252f83757b2b8304472371ca2f54ba5ec4508115dcbfa3064ba9d",
"transactionsRoot": "0xf66b162cb9486b7be07515baf93f804b6b1dabad64cb5890ce7876b2c7d9289a",
"receiptsRoot": "0xe989f5d7ac61663a4f2837bbcfbd086050ecfd72eff0140706abedab09630353",
"logsBloom": "0x4011000010001041…(256 bytes)",
"difficulty": "0x0",
"number": "0x2299a13",
"gasLimit": "0x10b07600",
"gasUsed": "0x305c78",
"timestamp": "0x6ace2efd",
"extraData": "0x010000006400000016000000000007a120",
"mixHash": "0x343885aaa605c1c6a90cd350e2290b584fa21d4309af3bf9154a590e8a02e1ff",
"nonce": "0x0000000000000000",
"baseFeePerGas": "0x7a120",
"withdrawalsRoot": "0xd97fde9b908a976e4a0fcf2f3b722f37fa80fbf7710b9072a5c82b5cef686ae2",
"blobGasUsed": "0x259450",
"excessBlobGas": "0x0",
"parentBeaconBlockRoot": "0x6a99d7aaa1b5aab20ed668b7b51114bbb94dbb6bc51ab652f258b8a25438a6cf",
"requestsHash": "0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
"size": "0x4301",
"uncles": [],
"transactions": "13 transactions",
"withdrawals": []
}Example request
curl -s https://rpc.swiftnodes.io/rpc/worldchain?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/worldchain?key=YOUR_API_KEY"),
});
// Header plus transaction hashes (2.6 KB)
const block = await client.getBlock({ blockTag: "latest" });
// With full transactions (57.4 KB on average on World Chain)
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 World Chain
- eth_blockNumberSupported
- eth_chainIdSupported
- eth_getBalanceSupported
- eth_getTransactionByHashNot available
- 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_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
- 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 World Chain support eth_getBlockByNumber?
Yes. eth_getBlockByNumber answered on the SwiftNodes World Chain endpoint when our weekly probe called it through the customer path (2026-10-13).
How many transactions are in each World Chain block?
In five consecutive blocks on 2026-10-13: 13, 16, 16, 22, 22.
World Chain endpoints, live block height and WebSocket status are on the World Chain RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.