RPC method

eth_getBlockByNumber on Berachain

Supported on SwiftNodes

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

Header fields27 (1 beyond the Ethereum set)
Transactions per block1, 1, 4, 2, 1 in five consecutive blocks
Response size, full transactions (true)4.7 KB average
Response size, hashes only (false)2.1 KB
Gas limit36,000,000
Gas used in the latest block0 (0.000% of the limit)
Base fee1.00 gwei
Tag "safe"block 27,440,135
Tag "finalized"block 27,440,135
Tag "pending"block 27,440,138
Tag "earliest"block 0

What is different on Berachain

Berachain blocks carry a field that Ethereum blocks do not. parentProposerPubkey: specific to this chain's node software, not part of the Ethereum JSON-RPC specification. Strict schema validators need to allow it.

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

5 of the 9 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.

A real Berachain block header

From block 27,440,133, as our endpoint returned it (long hex values shortened).

{
  "baseFeePerGas": "0x3b9aca00",
  "blobGasUsed": "0x0",
  "difficulty": "0x0",
  "excessBlobGas": "0x0",
  "extraData": "0x626572612d726574682f76312e342e342f6c696e7578",
  "gasLimit": "0x2255100",
  "gasUsed": "0x0",
  "hash": "0xb34d59f660d4d662a5d4e8fd27b5687764c668df2f54afdcb7914a018a1919cc",
  "logsBloom": "0x0000000000000000…(256 bytes)",
  "miner": "0x34f85ca372b5805570e180f4c7cf3da4c75213a8",
  "mixHash": "0x6ae1b0278714e4e174c569dd66a81be57474b7933f7d7bd4d8505ff4a08de10d",
  "nonce": "0x0000000000000000",
  "number": "0x1a2b405",
  "parentBeaconBlockRoot": "0x310d66684442398b44438490a998ebc7af7b3b685a430bd898f72ec4ba691a09",
  "parentHash": "0x55fbce8c4e4213e960e3cef54acc87e5aa52fec02a6ee19a2c2dd6d266f99087",
  "parentProposerPubkey": "0x90e5fba025da21db…(48 bytes)",
  "receiptsRoot": "0x469a05b03fc58a40b780f2dd96f78122f6962c52773f0c98614f690559b045f8",
  "requestsHash": "0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "size": "0x3a9",
  "stateRoot": "0x7c5cb220e37fe5076521db4419e469dd6e336d234b3abbee9ef7b508b47305b5",
  "timestamp": "0x6ace25c6",
  "transactions": "1 transactions",
  "transactionsRoot": "0xc7ccd7959ace5e2f7291f3cc5a85518292a8d21bc00da41e5ffeceb11af3c26e",
  "uncles": [],
  "withdrawals": [
    {
      "address": "0x1ae7dd7ae06f6c58b4524d9c1f816094b1bccd8e",
      "amount": "0x65a03c40",
      "index": "0xffffffffffffffff",
      "validatorIndex": "0xffffffffffffffff"
    }
  ],
  "withdrawalsRoot": "0xdb6ea1b4f38c2f3879628b83a10f587af9edc797eebce0bb5816280a8be8efae"
}

Example request

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

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

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

eth_getBlockByNumber on other chains

Frequently asked questions

Does Berachain support eth_getBlockByNumber?

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

How many transactions are in each Berachain block?

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

What are parentProposerPubkey in a Berachain block?

parentProposerPubkey is not part of the Ethereum JSON-RPC specification; added by this chain's node software.

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

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