RPC method

eth_getTransactionByHash on opBNB

Supported on SwiftNodes

Everything below was measured on 2026-10-13 by calling eth_getTransactionByHash on opBNB through the same endpoint customers use, and is re-measured weekly.

What eth_getTransactionByHash does

Returns a transaction by its hash: sender, recipient, value, input data, gas fields and signature, plus the block it was included in. It returns null for a hash the node does not know, and a transaction still in the mempool has a null blockNumber.

Transaction types on opBNB

Types of the 12 transactions in five consecutive blocks when we measured. Decoders that reject unknown types will fail on opBNB if any of these is missing from their list.

0x2 EIP-1559	7 (58%)
0x7e L1-to-L2 deposit (OP Stack)	5 (42%)

Fields beyond Ethereum's

Type 0x7e (L1-to-L2 deposit (OP Stack)) transactions carry extra fields. depositReceiptVersion: the version of the deposit receipt format; mint: the amount of ETH minted on L2 by a deposit; sourceHash: the unique ID of an L1-to-L2 deposit, derived from its L1 origin.

A real opBNB transaction

A type 0x2 transaction from one of the latest blocks, as our endpoint returned it (long hex values shortened).

{
  "blockHash": "0xbb83dca71344a50d6c90916983f0104a6984412c6d7ed32536d14134821fd8cc",
  "blockNumber": "0xba12756",
  "from": "0x91d286161a01870f7203472560e1552a10553094",
  "gas": "0x73d6",
  "gasPrice": "0x1",
  "maxFeePerGas": "0x1",
  "maxPriorityFeePerGas": "0x1",
  "hash": "0x2411ed50ae104799af0cb56ef9f53291ed6644a76ae609b59f984881d8686fd4",
  "input": "0xe95a644f000000000000000000000000000000000000000000000000192293bc26d1d787",
  "nonce": "0x31c",
  "to": "0xa40e1d8ea266387088ab3904d982d146e2727f34",
  "transactionIndex": "0x1",
  "value": "0x0",
  "type": "0x2",
  "accessList": [],
  "chainId": "0xcc",
  "v": "0x0",
  "r": "0xc772d85850e411191fb892d82305e8752eebee5cc06dcea0d21ca4469e91ddf2",
  "s": "0x25d40ed2c90237fcc81f462380207a031791ec1d7a26cfa39a0fa6faa238193b",
  "yParity": "0x0"
}

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_getTransactionByHash","params":["0x2411ed50ae104799af0cb56ef9f53291ed6644a76ae609b59f984881d8686fd4"]}'

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/opbnb?key=YOUR_API_KEY"),
});

const tx = await client.getTransaction({ hash: "0x2411ed50ae104799af0cb56ef9f53291ed6644a76ae609b59f984881d8686fd4" });
if (tx.blockNumber === null) console.log("still pending");
console.log(tx.type, tx.from, tx.to, tx.value);

Other methods on opBNB

eth_getTransactionByHash on other chains

Frequently asked questions

Does opBNB support eth_getTransactionByHash?

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

Which transaction types does opBNB use?

In five recent blocks: 5 × 0x7e (L1-to-L2 deposit (OP Stack)), 7 × 0x2 (EIP-1559).

Why does eth_getTransactionByHash return null on opBNB?

The node does not know the hash: it was never broadcast, it was dropped from the mempool, or it was sent to another chain. Check the hash and the chain ID before retrying.

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.