POST
/
evm
eth_getTransactionReceipt
curl --request POST \
  --url https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/evm \
  --header 'Content-Type: application/json' \
  --data '{
  "jsonrpc": "2.0",
  "method": "eth_getTransactionReceipt",
  "params": [
    "0x33c3321b162edac1fdbb53af2962b2940c07e334a4f5ff758f1d5ef1235e55d0"
  ],
  "id": 1
}'
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "transactionHash": "0x33c3321b162edac1fdbb53af2962b2940c07e334a4f5ff758f1d5ef1235e55d0",
    "transactionIndex": "0x0",
    "blockHash": "0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890",
    "blockNumber": "0x9d0c37",
    "from": "0xFC1286EeddF81d6955eDAd5C8D99B8Aa32F3D2AA",
    "to": "0x5555555555555555555555555555555555555555",
    "gasUsed": "0x5208",
    "cumulativeGasUsed": "0x5208",
    "contractAddress": null,
    "logs": [],
    "status": "0x1",
    "effectiveGasPrice": "0x3b9aca00",
    "type": "0x0"
  }
}
Returns the receipt of a transaction by its hash, containing execution results, gas usage, event logs, and transaction status. Use this to verify transaction execution and extract contract events.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • transactionHash (string, required) — The 32-byte hash of the transaction

​
Returns

Returns a transaction receipt object, or null if the transaction is not found or still pending. Transaction receipt:
  • transactionHash — Hash of the transaction
  • transactionIndex — Index in the block (hex string)
  • blockHash — Hash of containing block
  • blockNumber — Number of containing block (hex string)
  • from — Sender address
  • to — Receiver address (null for contract creation)
  • gasUsed — Actual gas used (hex string)
  • cumulativeGasUsed — Total gas used in block up to this transaction (hex string)
  • contractAddress — Created contract address (null if not contract creation)
  • logs — Array of event logs
  • status — Transaction status (0x0 for failure, 0x1 for success)
  • effectiveGasPrice — Actual gas price paid (hex string)
  • type — Transaction type (hex string)
Log object:
  • address — Contract address that emitted the log
  • topics — Array of indexed event parameters
  • data — Non-indexed event parameters
Transaction receipts are only available for mined transactions. Pending transactions return null.

​
Use cases

  • Transaction verification — Confirm transaction execution and success status
  • Event extraction — Process smart contract events and logs
  • Gas analysis — Analyze transaction costs and gas usage
  • Contract deployment — Verify contract creation and get addresses
  • Wallet applications — Display transaction results to users
  • DeFi protocols — Monitor protocol events and state changes

Body

application/json

Response

200 - application/json

Successful response with transaction receipt

The response is of type object.