RPC method

eth_getBlockByNumber on opBNB

Supported on SwiftNodes

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

Header fields	27 (1 beyond the Ethereum set)
Transactions per block	2, 7, 1, 1, 1 in five consecutive blocks
Response size, full transactions (true)	4.1 KB average
Response size, hashes only (false)	1.8 KB
Gas limit	100,000,000
Gas used in the latest block	76,270 (0.076% of the limit)
Base fee	0 wei
Tag "safe"	block 195,110,659
Tag "finalized"	block 195,110,659
Tag "pending"	block 195,110,778
Tag "earliest"	block 0

What is different on opBNB

opBNB blocks carry a field that Ethereum blocks do not. milliTimestamp: 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), but not those of Prague (EIP-7685 requests). Code that assumes Ethereum's current header shape must treat the missing ones as optional.

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 12 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 110 blocks (about 28 s) behind the head.

A real opBNB block header

From block 195,110,742, as our endpoint returned it (long hex values shortened).

{
  "baseFeePerGas": "0x0",
  "blobGasUsed": "0x0",
  "difficulty": "0x0",
  "excessBlobGas": "0x0",
  "extraData": "0x",
  "gasLimit": "0x5f5e100",
  "gasUsed": "0x129ee",
  "hash": "0xbb83dca71344a50d6c90916983f0104a6984412c6d7ed32536d14134821fd8cc",
  "logsBloom": "0x0000000000000000…(256 bytes)",
  "milliTimestamp": "0x1a1353df8ba",
  "miner": "0x4200000000000000000000000000000000000011",
  "mixHash": "0x00fa0102000000000000000000000000000000000000000000000000000000c8",
  "nonce": "0x0000000000000000",
  "number": "0xba12756",
  "parentBeaconBlockRoot": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "parentHash": "0x6b50b0fa4a404fb81fd2814de89255f8d70df4eabc4c33238f1bba0e4e2648b6",
  "receiptsRoot": "0x6922908cf4f79cf8a9b1c6188805c6137b92c05bd62cc69ec9399372691d80cb",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "size": "0x3d7",
  "stateRoot": "0xc07262013488179fd46772def382606623d95b87464d87f0849f0ae7a3a50a94",
  "timestamp": "0x6ace2458",
  "totalDifficulty": "0x0",
  "transactions": "2 transactions",
  "transactionsRoot": "0x87126c0184a3378a8fce7d265a54814df690447f2f6107bc7e425e8ea26f8a04",
  "uncles": [],
  "withdrawals": [],
  "withdrawalsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421"
}

Example request

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

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

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

eth_getBlockByNumber on other chains

Frequently asked questions

Does opBNB support eth_getBlockByNumber?

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

How many transactions are in each opBNB block?

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

What are milliTimestamp in a opBNB block?

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

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

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