TriportRPC
DashboardDocs

gettransactioninfobyid

POSThttps://triport.io/rpc/tron/wallet/gettransactioninfobyid

Returns confirmed execution information for a native Tron transaction identifier.

Tron mainnettron:rpcfree+; tron_read_rpc: 15 / 20 / 100 / 250 RPS (free / basic / pro / business; default, unmeasured)

gettransactioninfobyid looks up the execution information associated with a confirmed transaction identifier. The request uses a 32-byte hexadecimal ID without a 0x prefix.

Use this operation for confirmed execution results, not pending detection. Tron does not expose a public wallet mempool or pending-transaction queue. An empty wallet object for an unknown or not-yet-confirmed identifier is not a receipt.

Parameters

The JSON body contains one required transaction identifier.

valuestringrequired
Exactly 64 hexadecimal characters with no 0x prefix.

Response

The concrete response example is unknown because the contract has no response example or receipt-property schema. {} is a schema-valid placeholder and also represents why callers must distinguish an empty lookup from a receipt.

responseobject
Confirmed execution information; properties are not enumerated by the contract.

Errors

Wallet failures use HTTP status plus JSON. See Tron errors.

HTTPMeaningWhen it happens
400Bad requestvalue is missing or is not 64 hexadecimal characters.
401UnauthorizedThe API key is missing or invalid.
403ForbiddenThe scope or tier does not permit the request.
429Rate limitedThe tron_read_rpc budget is exceeded.

A successful empty object can mean the transaction is unknown or not confirmed; do not synthesize receipt fields from that outcome.

Examples

const response = await fetch("https://triport.io/rpc/tron/wallet/gettransactioninfobyid", {
  method: "POST",
  headers: { "x-token": process.env.TRIPORT_API_KEY, "Content-Type": "application/json" },
  body: JSON.stringify({ value: process.env.TRON_TRANSACTION_ID }),
});
const transactionInfo = await response.json();

Notes

  • The transaction ID has no 0x prefix in this wallet request.
  • The operation is for confirmed execution information, not pending state.
  • No public wallet mempool endpoint is part of the Tron product surface.