RPC method

eth_getBlockByNumber on Cronos

Supported on SwiftNodes

Everything below was measured on 2026-10-13 by calling eth_getBlockByNumber on Cronos 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 Cronos: what we measured

Header fields	20
Transactions per block	0, 0, 2, 2, 4 in five consecutive blocks
Response size, full transactions (true)	3.1 KB average
Response size, hashes only (false)	1.4 KB
Gas limit	60,000,000
Gas used in the latest block	0 (0.000% of the limit)
Base fee	375 gwei
Tag "safe"	block 99,667,459
Tag "finalized"	block 99,667,463
Tag "pending"	block 99,667,465
Tag "earliest"	not served (null)

What is different on Cronos

The header includes the fields added by London (EIP-1559 base fee), but not those of Shanghai (withdrawals), Cancun (EIP-4844 blob gas), 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 2.2 times larger than hashes only. If you need only some transactions, fetch hashes and request those transactions or their receipts individually.

A real Cronos block header

From block 99,667,447, as our endpoint returned it (long hex values shortened).

{
  "baseFeePerGas": "0x574fbde600",
  "difficulty": "0x0",
  "extraData": "0x",
  "gasLimit": "0x3938700",
  "gasUsed": "0x0",
  "hash": "0x66f23a3daeb511d84d3772cfcfab51195f438804dff7053298688be7f0c6ea2e",
  "logsBloom": "0x0000000000000000…(256 bytes)",
  "miner": "0x652cd577175ab6370eaca144ca9f60fd7214a764",
  "mixHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "nonce": "0x0000000000000000",
  "number": "0x5f0cdf7",
  "parentHash": "0x9696ea3f2e451da827e5dd6c069d832e3aa1fcf698e7ef461f25a0c649134556",
  "receiptsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "size": "0x60d",
  "stateRoot": "0xa09fd363e390abfab8c1faae9dfd56cbb43007a0a75d875b8fcb9932dcb2d0aa",
  "timestamp": "0x6ace23f6",
  "transactions": "0 transactions",
  "transactionsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  "uncles": []
}

Example request

curl -s https://rpc.swiftnodes.io/rpc/cronos?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/cronos?key=YOUR_API_KEY"),
});

// Header plus transaction hashes (1.4 KB)
const block = await client.getBlock({ blockTag: "latest" });

// With full transactions (3.1 KB on average on Cronos)
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 Cronos

eth_getBlockByNumber on other chains

Frequently asked questions

Does Cronos support eth_getBlockByNumber?

Yes. eth_getBlockByNumber answered on the SwiftNodes Cronos endpoint when our weekly probe called it through the customer path (2026-10-13).

How many transactions are in each Cronos block?

In five consecutive blocks on 2026-10-13: 0, 0, 2, 2, 4.

Cronos endpoints, live block height and WebSocket status are on the Cronos RPC page.

One key covers every chain we serve, and SwiftNodes has a free tier.