RPC method

eth_getBlockByNumber on Ink

Supported on SwiftNodes

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

Header fields	26
Transactions per block	8, 8, 13, 7, 12 in five consecutive blocks
Response size, full transactions (true)	20.8 KB average
Response size, hashes only (false)	2.3 KB
Gas limit	30,000,000
Gas used in the latest block	705,601 (2.4% of the limit)
Base fee	299 wei
Tag "safe"	block 58,397,351
Tag "finalized"	block 58,396,309
Tag "pending"	block 58,397,843
Tag "earliest"	block 0

What is different on Ink

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 9.2 times larger than hashes only. If you need only some transactions, fetch hashes and request those transactions or their receipts individually.

5 of the 48 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 1,532 blocks (about 26 min) behind the head.

A real Ink block header

From block 58,397,835, as our endpoint returned it (long hex values shortened).

{
  "baseFeePerGas": "0x12b",
  "blobGasUsed": "0xdccd0",
  "difficulty": "0x0",
  "excessBlobGas": "0x0",
  "extraData": "0x01000000fa000000060000000000000000",
  "gasLimit": "0x1c9c380",
  "gasUsed": "0xac441",
  "hash": "0x5cb07e69a859ab1367fa04c6651667145aac8f878d08608ced8f9ba13620aa09",
  "logsBloom": "0x0000000000000000…(256 bytes)",
  "miner": "0x4200000000000000000000000000000000000011",
  "mixHash": "0x24246ec6c741c3ce92efd15a14c88922d8c8ac3dbbec7928447181e9d75b76ea",
  "nonce": "0x0000000000000000",
  "number": "0x37b148b",
  "parentBeaconBlockRoot": "0xcea047d38b7b028ce606eb16a83ab63c95f6f0217c8f1cf04a8f85a6dae95b8a",
  "parentHash": "0xa86d359414fcd455071114d8f677b14ebd5d6f3e5ee96ecc4109563efb4f01f6",
  "receiptsRoot": "0x28e43df4f7ac975a1ec557841159effe492f559eda7c14991646773ceca7efb4",
  "requestsHash": "0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "size": "0x14d2",
  "stateRoot": "0x1beb6772f9a78041f4dabef3328586b1820eb041313d9d93761fc329c3ddaefc",
  "timestamp": "0x6ace2ab6",
  "transactions": "8 transactions",
  "transactionsRoot": "0x1789aca9fe0e7e0802c5a205a601372777b7df69237af573d6fb3c4952108fe3",
  "uncles": [],
  "withdrawals": [],
  "withdrawalsRoot": "0x3c18f757394bfea5ad6fb7bad24b941725b6fb94a4bc81750527c323e0058e9c"
}

Example request

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

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

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

eth_getBlockByNumber on other chains

Frequently asked questions

Does Ink support eth_getBlockByNumber?

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

How many transactions are in each Ink block?

In five consecutive blocks on 2026-10-13: 8, 8, 13, 7, 12.

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

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