RPC method

eth_getBlockByNumber on Shibarium

Supported on SwiftNodes

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

Header fields	21
Transactions per block	0, 1, 0, 0, 0 in five consecutive blocks
Response size, full transactions (true)	1.8 KB average
Response size, hashes only (false)	1.6 KB
Gas limit	20,000,000
Gas used in the latest block	0 (0.000% of the limit)
Base fee	15 wei
Tag "safe"	block 19,410,838
Tag "finalized"	block 19,410,838
Tag "pending"	block 19,410,860
Tag "earliest"	block 0

What is different on Shibarium

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.

"finalized" was 21 blocks (about 2 min) behind the head.

A real Shibarium block header

From block 19,410,858, as our endpoint returned it (long hex values shortened).

{
  "baseFeePerGas": "0xf",
  "difficulty": "0x3",
  "extraData": "0xd88301030983626f…(100 bytes)",
  "gasLimit": "0x1312d00",
  "gasUsed": "0x0",
  "hash": "0xf3011a42af67b9a6597960fe8e020fd19864b1931bb28035808b208b49b891dd",
  "logsBloom": "0x0000000000000000…(256 bytes)",
  "miner": "0x0000000000000000000000000000000000000000",
  "mixHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "nonce": "0x0000000000000000",
  "number": "0x1282faa",
  "parentHash": "0x8c6685a1f0a4743e0d75454b3c1ef96d5ed12f21d1308776e24b69d3bea8ceef",
  "receiptsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "size": "0x267",
  "stateRoot": "0xb92d8b72baab8d10ad269e6c4d74105588a8c2300c4a1215cd7b86d1945673d8",
  "timestamp": "0x6ace2f51",
  "totalDifficulty": "0x3bab67b",
  "transactions": "0 transactions",
  "transactionsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  "uncles": []
}

Example request

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

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

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

eth_getBlockByNumber on other chains

Frequently asked questions

Does Shibarium support eth_getBlockByNumber?

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

How many transactions are in each Shibarium block?

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

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

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