RPC method

eth_getBlockByNumber on Soneium

Supported on SwiftNodes

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

Header fields	26
Transactions per block	5, 5, 2, 4, 4 in five consecutive blocks
Response size, full transactions (true)	12.7 KB average
Response size, hashes only (false)	2.1 KB
Gas limit	40,000,000
Gas used in the latest block	925,099 (2.3% of the limit)
Base fee	0.0130 gwei
Tag "safe"	block 29,380,167
Tag "finalized"	block 29,379,505
Tag "pending"	block 29,380,248
Tag "earliest"	block 0

What is different on Soneium

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

5 of the 20 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 742 blocks (about 25 min) behind the head.

A real Soneium block header

From block 29,380,244, as our endpoint returned it (long hex values shortened).

{
  "hash": "0x1ab692bd507f060a1b0aae574ca41a46ab3518fc583e5ac699d46155da025d7c",
  "parentHash": "0xd04cb3689abb435c5e0cdcaf1302ce17b6d69a4e530d7235e0b936024cc980ad",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "miner": "0x4200000000000000000000000000000000000011",
  "stateRoot": "0xe9247d5fce6040a4cbb5f3ed2df259e314a1f590c0b87f8391e83228964ae99b",
  "transactionsRoot": "0x221bd8aed72654489ece655ef77395549b22c6a0563aee253d30fcd716812160",
  "receiptsRoot": "0x742ca3b92e74d5435a7fbfb04f8d2d6c9beac18407903cedd8e27d664375703f",
  "logsBloom": "0x0000040000000000…(256 bytes)",
  "difficulty": "0x0",
  "number": "0x1c04e94",
  "gasLimit": "0x2625a00",
  "gasUsed": "0xe1dab",
  "timestamp": "0x6ace26c7",
  "extraData": "0x01000000fa0000000a0000000000c65d40",
  "mixHash": "0xa61eba6ad1e628cf7be97863b9bc9b50270f491f902ac8319aad6f7fb6463a99",
  "nonce": "0x0000000000000000",
  "baseFeePerGas": "0xc65d40",
  "withdrawalsRoot": "0xe227b11dee9e7e60ca24ace97e2ff95b2644bc9e3a8b4de1b8e220b60b24cac3",
  "blobGasUsed": "0xa7c60",
  "excessBlobGas": "0x0",
  "parentBeaconBlockRoot": "0x4f6a8968675d065a7edb12e04c8cd2cb5045c90ea1aa636c39f0a47288dd80b0",
  "requestsHash": "0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
  "size": "0x19dd",
  "uncles": [],
  "transactions": "5 transactions",
  "withdrawals": []
}

Example request

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

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

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

eth_getBlockByNumber on other chains

Frequently asked questions

Does Soneium support eth_getBlockByNumber?

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

How many transactions are in each Soneium block?

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

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

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