RPC method

eth_getBlockByNumber on Taiko

Supported on SwiftNodes

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

Header fields	26
Transactions per block	1, 1, 1, 1, 1 in five consecutive blocks
Response size, full transactions (true)	2.6 KB average
Response size, hashes only (false)	1.8 KB
Gas limit	46,000,000
Gas used in the latest block	112,056 (0.244% of the limit)
Base fee	0.0100 gwei
Tag "safe"	block 12,625,171
Tag "finalized"	block 12,625,171
Tag "pending"	block 12,625,970
Tag "earliest"	block 0

What is different on Taiko

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 797 blocks (about 27 min) behind the head.

A real Taiko block header

From block 12,625,965, as our endpoint returned it (long hex values shortened).

{
  "hash": "0x46e5905c453ec95b9b2195d29849761132ba13f68d72259eb3024a7289ef8735",
  "parentHash": "0xdc42370db045fd3aee6f2b42deab429b140713a490b54847a5e0ade6256dfc2f",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "miner": "0x35376dd47c061bc3b8c8e8d61987019e7ed58f06",
  "stateRoot": "0x53e60757abc99749475f173b80dde60455b059dca3bf314e008da78ddb067d52",
  "transactionsRoot": "0x806687830644849a6ed2fd184c773a20ac560dcb40bac064f438e9bea2cfafe3",
  "receiptsRoot": "0x1e876d09e90483e29c75a24436114b7b0dc94735f2bd92d0d1b19c4edf43bc28",
  "logsBloom": "0x0000000000000000…(256 bytes)",
  "difficulty": "0x11b632",
  "number": "0xc0a82d",
  "gasLimit": "0x2bde780",
  "gasUsed": "0x1b5b8",
  "timestamp": "0x6ace2629",
  "extraData": "0x4b00000000a35b",
  "mixHash": "0xeaae2384d712278f0e8c1134b996ee6485aceb68f4bf13124ae87b782fc809a3",
  "nonce": "0x0000000000000000",
  "baseFeePerGas": "0x989680",
  "withdrawalsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  "blobGasUsed": "0x0",
  "excessBlobGas": "0x0",
  "parentBeaconBlockRoot": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "requestsHash": "0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
  "size": "0x34e",
  "uncles": [],
  "transactions": "1 transactions",
  "withdrawals": []
}

Example request

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

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

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

eth_getBlockByNumber on other chains

Frequently asked questions

Does Taiko support eth_getBlockByNumber?

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

How many transactions are in each Taiko block?

In five consecutive blocks on 2026-10-13: 1, 1, 1, 1, 1.

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

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