eth_getTransactionReceipt

eth_getTransactionReceipt returns the execution receipt for a transaction once it has been mined into a Polygon PoS block, where gas is paid in the network's native MATIC. The receipt is the authoritative record of what happened on-chain: it tells you whether the transaction succeeded or reverted, how much gas it burned, the effective gas price it paid, and every event (log) the call emitted. Send the request to https://polygon.therpc.io/YOUR_API_KEY (chain ID 137, 0x89). Because Polygon seals blocks roughly every two seconds, a receipt usually becomes available within a few seconds of submission.

Use cases

• Confirm whether a Polygon transaction succeeded (status: "0x1") or reverted (status: "0x0") once it lands in a block.
• Decode the logs array to pick up emitted events — for example a Transfer from the USDT contract at 0xc2132D05D31c914a87C6611C10748AEb04B58e8F — and update your application state.
• Read contractAddress to learn the address of a contract you just deployed; it is non-null only for contract-creation transactions.
• Compute the exact fee paid in MATIC as gasUsed * effectiveGasPrice, useful for accounting given Polygon's typically low per-transaction cost.

Parameters

Response

Example request

1curl https://polygon.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5    "jsonrpc": "2.0",
6    "method": "eth_getTransactionReceipt",
7    "params": ["0x0000000000000000000000000000000000000000000000000000000000000000"],
8    "id": 1
9  }'

Try it live in the Polygon playground.

Errors & troubleshooting

Common pitfalls

• The call returns null for a transaction still sitting in the mempool. Poll until you get a non-null receipt rather than assuming it is ready — on Polygon this is usually only a couple of blocks (a few seconds), but congestion can stretch it.
• A status of "0x0" means the transaction was included in a block but reverted; the sender still paid for the gas it consumed in MATIC, so always check status before treating an action as successful.
• When ingesting every receipt in a block, eth_getBlockReceipts returns them all in one round trip and is far more efficient than firing one eth_getTransactionReceipt per hash — valuable on a high-throughput chain like Polygon.

Supported networks

• Mainnet — Chain ID: 137
• Amoy — Chain ID: 80002

See also

• eth_getTransactionByHash
• eth_getBlockReceipts
• eth_getLogs

1curl https://polygon.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H 'Content-Type: application/json' \
4  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getTransactionReceipt","params":[""]}'