TriportRPC

eth_getTransactionReceipt

POSThttps://triport.io/rpc/bsc

Return a transaction receipt by hash.

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

eth_getTransactionReceipt returns the execution receipt for a BNB Smart Chain transaction hash, or null when no receipt is available.

Use it after mining to inspect status, gas usage, effective gas price, logs, and a created contract address. Receipt quantities and byte fields use standard EVM JSON-RPC encodings.

Unlike eth_getTransactionByHash, this method describes execution outcome rather than the submitted transaction. It is read-only; raw transaction submission is not exposed for BSC.

Parameters

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

transactionHashstring (32-byte hex hash)required
The 32-byte hash of the transaction to query.

Response

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

resultobject or null
Receipt object, or null when unavailable.
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 or null
Destination address, or null for contract creation.
result.contractAddressstring or null
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.
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_getTransactionReceipt",
    "params": [
      "0x0000000000000000000000000000000000000000000000000000000000000000"
    ]
  }),
});


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

Notes

  • A pending or unknown transaction can produce null; poll according to your application's confirmation policy.
  • The BSC categories use configured defaults of 15 / 20 / 100 / 250 RPS; they are marked unmeasured in the tier matrix.
  • Related methods: eth_getTransactionByHash, eth_getBlockReceipts, eth_getLogs.