RPC method

eth_getTransactionReceipt on opBNB

Supported on SwiftNodes

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

What eth_getTransactionReceipt does

Returns the outcome of a mined transaction: status (1 success, 0 reverted), gas used, the effective gas price, the logs it emitted and any contract it created. It returns null until the transaction is in a block.

eth_getTransactionReceipt on opBNB: what we measured

Fields	20 (6 beyond the Ethereum set)
Receipt for an unknown hash	null
Size of the sample receipt	1.6 KB

Reading the fee and fields

Beyond the Ethereum fields, opBNB receipts carry 6 more. l1GasPrice: the Ethereum base fee the L1 fee was priced with; l1GasUsed: the L1 gas the transaction's compressed data was estimated to use; l1Fee: the L1 data fee in wei, charged on top of gasUsed × effectiveGasPrice. Add it to get the real cost; l1BlobBaseFee: the Ethereum blob base fee the L1 fee was priced with; l1BaseFeeScalar: the weight of Ethereum's execution base fee in the L1 fee (post-Ecotone formula); l1BlobBaseFeeScalar: the weight of Ethereum's blob base fee in the L1 fee.

gasUsed × effectiveGasPrice is not the whole cost on opBNB. In the sample receipt below, execution cost 29,631 wei and the L1 data fee (l1Fee) 5,984,000,065 wei, so 99.9% of what the sender paid was the L1 fee. A wallet or accounting tool that ignores l1Fee understates fees.

A hash the node has not seen returns null, not an error, so poll until it is non-null (viem's waitForTransactionReceipt does this) and give up after a timeout.

A real opBNB receipt

As our endpoint returned it; logs collapsed to a count and long hex values shortened.

{
  "type": "0x2",
  "from": "0x91d286161a01870f7203472560e1552a10553094",
  "to": "0xa40e1d8ea266387088ab3904d982d146e2727f34",
  "status": "0x1",
  "cumulativeGasUsed": "0x129ee",
  "logsBloom": "0x0000000000000000…(256 bytes)",
  "logs": "1 logs",
  "transactionHash": "0x2411ed50ae104799af0cb56ef9f53291ed6644a76ae609b59f984881d8686fd4",
  "contractAddress": null,
  "gasUsed": "0x73bf",
  "blockHash": "0xbb83dca71344a50d6c90916983f0104a6984412c6d7ed32536d14134821fd8cc",
  "blockNumber": "0xba12756",
  "transactionIndex": "0x1",
  "effectiveGasPrice": "0x1",
  "l1GasPrice": "0x3473bc0",
  "l1GasUsed": "0x640",
  "l1Fee": "0x164ac9841",
  "l1BlobBaseFee": "0x1",
  "l1BaseFeeScalar": "0x109a0",
  "l1BlobBaseFeeScalar": "0x9fe98"
}

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

import { createPublicClient, http } from "viem";

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

const receipt = await client.waitForTransactionReceipt({ hash, timeout: 60_000 });
if (receipt.status !== "success") throw new Error("reverted");

// Total cost on opBNB: execution plus the L1 data fee
const execution = receipt.gasUsed * receipt.effectiveGasPrice;
const total = execution + (receipt.l1Fee ?? 0n);

Other methods on opBNB

eth_getTransactionReceipt on other chains

Frequently asked questions

Does opBNB support eth_getTransactionReceipt?

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

How do I get the total fee of a transaction on opBNB?

Add the receipt's l1Fee to gasUsed × effectiveGasPrice.

Why is the opBNB receipt null?

The transaction is not in a block yet, or the hash is unknown to the node. Keep polling with a timeout.

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.