TriportRPC

eth_getBlockReceipts

POSThttps://triport.io/rpc/bsc

Return all transaction receipts in a block.

BNB Smart Chainbsc:rpcbsc_read_rpc_heavy - 15 / 20 / 100 / 250 RPS (free / basic / pro / business) (default, unmeasured); enterprise unlimited

eth_getBlockReceipts returns an array containing the transaction receipts for one BNB Smart Chain block.

Use it when an indexer needs status, gas, logs, and contract-creation results for the complete block without looking up every receipt separately. The block is selected with a standard tag or hex block number.

Unlike eth_getTransactionReceipt, this method is block-scoped and can return many receipts. Unlike eth_getLogs, it returns receipt objects rather than only matching event logs.

Parameters

JSON-RPC params is a positional array: [block].

blockstring (block tag or hex quantity)required
Block selector: latest, earliest, pending, or an EVM hex block number.

Response

The response below is the checked fixture for this method; it is reproduced without changing its fields or values.

resultarray<object>
Transaction receipts returned for the block.
result[].transactionHashstring
Transaction hash.
result[].transactionIndexstring
Transaction index as a hex quantity.
result[].blockHashstring
Containing block hash.
result[].blockNumberstring
Containing block number as a hex quantity.
result[].fromstring
Sender address.
result[].tostring
Destination address, or null for contract creation.
result[].contractAddressstring
Created contract address when applicable.
result[].cumulativeGasUsedstring
Cumulative block gas used as a hex quantity.
result[].gasUsedstring
Transaction gas used as a hex quantity.
result[].effectiveGasPricestring
Effective gas price as a hex quantity.
result[].logsarray<object>
Event logs emitted by the transaction.
result[].logsBloomstring
Receipt logs bloom as hex data.
result[].statusstring
Execution status as a hex quantity.
result[].typestring
Transaction type as a hex quantity.

Errors

Errors use the standard JSON-RPC error envelope. See BSC errors for network-specific classification and the linked shared reference.

CodeMeaningWhen it happens
-32602Invalid paramsA required positional parameter is missing or a value does not match the OpenRPC schema.
-32000Upstream request failureInterpret the message with the code: header not found means a missing block; pruned/unsupported state text means unavailable historical state.
401UnauthorizedThe x-token API key is missing or invalid.
429Rate limitedThe request exceeds the configured category RPS for the caller's tier.

Examples

JavaScript (fetch)

const response = await fetch("https://triport.io/rpc/bsc", {
  method: "POST",
  headers: {
    "x-token": process.env.TRIPORT_API_KEY,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "jsonrpc": "2.0",
    "id": 1,
    "method": "eth_getBlockReceipts",
    "params": [
      "latest"
    ]
  }),
});


const payload = await response.json();
console.log(payload.result);

Notes