Overview

This node interacts with blockchain networks via QuickNode RPC endpoints to retrieve the transaction receipt for a given transaction hash. It is useful for developers and blockchain analysts who need to verify the status and details of a specific transaction on the blockchain, such as whether the transaction was successful, the amount of gas used, and the block number it was included in.

Use Case Examples

1. A developer wants to confirm if a transaction they submitted to the Ethereum network was successful and how much gas was consumed.
2. A blockchain analyst needs to fetch detailed receipt information for a transaction hash to audit or monitor transaction outcomes.

Properties

Output

JSON

• resource - The resource type, here it is 'blockchain'.
• operation - The operation performed, here it is 'getTransactionReceipt'.
• result - The raw transaction receipt data returned from the blockchain.
• timestamp - The ISO timestamp when the data was retrieved.
• status - The status of the transaction receipt, parsed as an integer (e.g., 1 for success, 0 for failure).
• gasUsed - The amount of gas used by the transaction, parsed as an integer.
• blockNumber - The block number in which the transaction was included, parsed as an integer.

Dependencies

• QuickNode API endpoint URL credential

Troubleshooting

• Invalid transaction hash format may cause the API to return an error. Ensure the transaction hash is a valid hexadecimal string starting with '0x'.
• If the transaction receipt is not found, the transaction hash might be incorrect or the transaction might not yet be mined.
• API errors from QuickNode are surfaced with their message; check your API endpoint URL and credentials for correctness.
• Invalid JSON in transaction object (for other operations) will throw an error; ensure JSON inputs are correctly formatted.

Links

• QuickNode eth_getTransactionReceipt API - Official QuickNode documentation for the eth_getTransactionReceipt RPC method used to get transaction receipts.