Queries a transaction execution receipt by transaction ID. This SolidityNode version returns only receipts for solidified transactions.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Queries a transaction execution receipt by transaction ID. This SolidityNode version returns only receipts for solidified transactions.
Difference from GetTransactionByIdThis API returns the post-execution receipt: fees, Energy usage, contract execution status, event logs, internal transactions, and related execution data. GetTransactionById returns the transaction body submitted by the requester:
raw_dataand signatures. Use both APIs together to get the complete state of a transaction.
Confirmation semantics
The response is the transaction's post-execution receipt. When SolidityNode returns this receipt, the block containing the transaction has been solidified. For a plain TRX transfer, the TransferContract in the transaction body already contains the amount and recipient. This API is mainly used to confirm that the transaction has entered solidified state. For smart-contract transactions, read the receipt to determine the actual execution result.
Usage notes
Use this API to confirm the final execution status of smart-contract transactions. receipt.result = SUCCESS indicates successful contract execution. If the receipt is not found, do not immediately classify the transaction as failed. Continue confirming with the transaction expiration window and solidified block scan results.
For the complete deposit detection, TRC-20 Event parsing, and internal transaction parsing flow, see Block-based deposit monitoring.
Related resources
- GetTransactionInfoById (FullNode) — FullNode version
- GetTransactionById — query the transaction body
- API signature and broadcast flow — complete construction, broadcast, and solidified-confirmation path
- Confirmation semantics — distinguish transaction body, execution receipt, and solidified receipt
- Block-based deposit monitoring — deposit detection, TRC-20 Event, and internal transaction parsing flow
- Contract calls and Energy billing — source of receipt fields such as
energy_usageandenergy_fee