eth_getBlockByNumber on Kaia
Everything below was measured on 2026-10-13 by calling eth_getBlockByNumber on Kaia 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 Kaia: what we measured
| Header fields | 23 (1 beyond the Ethereum set) |
|---|---|
| Transactions per block | 1, 5, 4, 2, 3 in five consecutive blocks |
| Response size, full transactions (true) | 35.1 KB average |
| Response size, hashes only (false) | 1.7 KB |
| Gas limit | 500,000,000 |
| Gas used in the latest block | 49,629 (0.010% of the limit) |
| Base fee | 25.00 gwei |
| Tag "safe" | block 229,692,880 |
| Tag "finalized" | block 229,692,881 |
| Tag "pending" | block 229,692,884 |
| Tag "earliest" | block 0 |
What is different on Kaia
Kaia blocks carry a field that Ethereum blocks do not. randomReveal: specific to this chain's node software, not part of the Ethereum JSON-RPC specification. Strict schema validators need to allow it.
The header includes the fields added by London (EIP-1559 base fee), Cancun (EIP-4844 blob gas), but not those of Shanghai (withdrawals), Cancun (EIP-4788 beacon root), Prague (EIP-7685 requests). Code that assumes Ethereum's current header shape must treat the missing ones as optional.
Asking for full transactions (second parameter true) made the response 20.6 times larger than hashes only. If you need only some transactions, fetch hashes and request those transactions or their receipts individually.
A real Kaia block header
From block 229,692,872, as our endpoint returned it (long hex values shortened).
{
"baseFeePerGas": "0x5d21dba00",
"blobGasUsed": "0x0",
"difficulty": "0x1",
"excessBlobGas": "0x0",
"extraData": "0x",
"gasLimit": "0x1dcd6500",
"gasUsed": "0xc1dd",
"hash": "0x43e6cc1260ef662da1e091ce7728d7f4871f75fc7bd1452827bb80e54a2077e9",
"logsBloom": "0x0000000000000000…(256 bytes)",
"miner": "0xbca8ffa45cc8e30bbc0522cdf1a1e0ebf540dfe2",
"mixHash": "0x8e1ee6cefb3fee16b32f79cdf0e8b77dd79f10a8ffe3caa61bc9b0900c02ed6f",
"nonce": "0x0000000000000000",
"number": "0xdb0d5c8",
"parentHash": "0xaeef402de55d41097ff9945fca77b48c72a8d287199c47c33dd92c70f22331c3",
"randomReveal": "0xa1eb9acfeddf40c1…(96 bytes)",
"receiptsRoot": "0x53dc7a3cb4ab1709a5c5dcad460847530024b99c131262af2f13ee61d30be2be",
"sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
"size": "0xbe3",
"stateRoot": "0xef3f8e206c7ada8533e395e22d3636a0e373c71f50e0c1c3545e99309be37473",
"timestamp": "0x6ace2827",
"transactions": "1 transactions",
"transactionsRoot": "0x782499f265b300779c6e407aff229018f5d764da058ecacc7ef7030811292fbb",
"uncles": []
}Example request
curl -s https://rpc.swiftnodes.io/rpc/kaia?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/kaia?key=YOUR_API_KEY"),
});
// Header plus transaction hashes (1.7 KB)
const block = await client.getBlock({ blockTag: "latest" });
// With full transactions (35.1 KB on average on Kaia)
const full = await client.getBlock({ blockNumber: block.number, includeTransactions: true });
// A block that will not be reorganised
const final = await client.getBlock({ blockTag: "finalized" });Other methods on Kaia
- 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_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
- 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 Kaia support eth_getBlockByNumber?
Yes. eth_getBlockByNumber answered on the SwiftNodes Kaia endpoint when our weekly probe called it through the customer path (2026-10-13).
How many transactions are in each Kaia block?
In five consecutive blocks on 2026-10-13: 1, 5, 4, 2, 3.
What are randomReveal in a Kaia block?
randomReveal is not part of the Ethereum JSON-RPC specification; added by this chain's node software.
Kaia endpoints, live block height and WebSocket status are on the Kaia RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.