eth_getBlockByNumber on Chiliz
Everything below was measured on 2026-10-13 by calling eth_getBlockByNumber on Chiliz 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 Chiliz: what we measured
| Header fields | 28 (1 beyond the Ethereum set) |
|---|---|
| Transactions per block | 1, 1, 3, 1, 1 in five consecutive blocks |
| Response size, full transactions (true) | 3.7 KB average |
| Response size, hashes only (false) | 2.6 KB |
| Gas limit | 55,000,000 |
| Gas used in the latest block | 107,185 (0.195% of the limit) |
| Base fee | 2500 gwei |
| Tag "safe" | block 0 |
| Tag "finalized" | block 0 |
| Tag "pending" | block 38,375,299 |
| Tag "earliest" | block 0 |
What is different on Chiliz
Chiliz blocks carry a field that Ethereum blocks do not. milliTimestamp: 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), 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.
"finalized" was 38,375,298 blocks (about 31979.4 hours) behind the head.
A real Chiliz block header
From block 38,375,296, as our endpoint returned it (long hex values shortened).
{
"baseFeePerGas": "0x246139ca800",
"blobGasUsed": "0x0",
"difficulty": "0x2",
"excessBlobGas": "0x0",
"extraData": "0xdb83020905883734…(411 bytes)",
"gasLimit": "0x3473bc0",
"gasUsed": "0x1a2b1",
"hash": "0x5e1bb6929317a35042d41ec72a93f80d43e65021d4402e3eb24cd83e6cedaf05",
"logsBloom": "0x0000000000000000…(256 bytes)",
"milliTimestamp": "0x1a13546ae38",
"miner": "0xa4c864e043ba00843fd502d85896c96ba5738c4c",
"mixHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
"nonce": "0x0000000000000000",
"number": "0x2498f80",
"parentBeaconBlockRoot": "0x0000000000000000000000000000000000000000000000000000000000000000",
"parentHash": "0x766fc88955a1e634ada61a49d42bfa95ef62eb482d9e36b0f72523937affcd34",
"receiptsRoot": "0x2259879f2546f31e23b15d21194fa8490ef480c83466ae4162234ab547971d65",
"requestsHash": "0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
"sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
"size": "0x4ea",
"stateRoot": "0xd44dc2309616a94db1cc47e8ff14c3eb109e6e105b11935b6452d0529097e2c3",
"timestamp": "0x6ace2693",
"totalDifficulty": "0x48b11a4",
"transactions": "1 transactions",
"transactionsRoot": "0xbec78175a5499328165b51daf6021d14b8957b3aff4b769119d2e5a9cc5cc812",
"uncles": [],
"withdrawals": [],
"withdrawalsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421"
}Example request
curl -s https://rpc.swiftnodes.io/rpc/chiliz?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/chiliz?key=YOUR_API_KEY"),
});
// Header plus transaction hashes (2.6 KB)
const block = await client.getBlock({ blockTag: "latest" });
// With full transactions (3.7 KB on average on Chiliz)
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 Chiliz
- 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
- 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
- Telos EVM
- Tempo
- Cronos
- Manta Pacific
- Shibarium
- Boba Network
- Arbitrum Nova
- Immutable zkEVM
Frequently asked questions
Does Chiliz support eth_getBlockByNumber?
Yes. eth_getBlockByNumber answered on the SwiftNodes Chiliz endpoint when our weekly probe called it through the customer path (2026-10-13).
How many transactions are in each Chiliz block?
In five consecutive blocks on 2026-10-13: 1, 1, 3, 1, 1.
What are milliTimestamp in a Chiliz block?
milliTimestamp is not part of the Ethereum JSON-RPC specification; added by this chain's node software.
Chiliz endpoints, live block height and WebSocket status are on the Chiliz RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.