Docs
Docs
Home
Getting Started
Agent Tooling
CLI
Supported Chains
Acala
Aptos
Arbitrum
Arc
Asset Hub
Astar
Avalanche
Base
Berachain
Bifrost
Binance Smart Chain
Bittensor
Blast
Boba Network
Bridge Hub
Celo
Centrifuge
Chiliz
Cronos
Enjin
Ethereum
Etherlink
Flow EVM Gateway
Gnosis
Hydration
Hyperliquid
Immutable
Ink
IoTeX
Kusama
Linea
LISK
Manta Atlantic
Manta Pacific
Mantle
MegaETH
Monad
Movement
Neuroweb
opBNB
Optimism
Plasma
Polkadot
Polygon
Pulsechain
Robinhood
Ronin
Scroll
Sonic
Starknet
Taiko
Tempo
Sui
TRON
Unichain
Viction
World Chain
XDC Network
XX Network
Zetachain
zkSync Era
Zora
Supported ChainsStarknetJSON-RPC API

starknet_getTransactionReceipt - Get Transaction Receipt

Get the execution receipt for a Starknet transaction by hash. Returns status, fees, events, and execution details for transaction verification and monitoring.

Starknet RPC endpoint: endpoint URLs, plans and pricing.

Returns the receipt of a transaction identified by its hash. The receipt includes execution status, actual fee paid, emitted events, and block inclusion details. This is the primary method for confirming whether a transaction succeeded or reverted.

Overview

After a transaction is submitted to Starknet, it goes through several stages: RECEIVED, ACCEPTED_ON_L2, and finally ACCEPTED_ON_L1 (once the proof is verified on Ethereum). The transaction receipt reflects the current status and provides detailed execution results.

Starknet transaction receipts differ from EVM receipts in several ways:

  • Fees are denominated in STRK or ETH (depending on the fee token used)
  • Events use felt252 keys and data values (Cairo's native field element type)
  • Execution status distinguishes between SUCCEEDED and REVERTED
  • L2-to-L1 messages emitted during execution are tracked in messages_sent
  • execution_resources reports fee-relevant buckets such as l1_gas, l2_gas, and l1_data_gas
JSON-RPC request
{
  "jsonrpc": "2.0",
  "method": "starknet_getTransactionReceipt",
  "params": [
    "0x1438e2dc065c46840a28564c4c0a0db0bd43a9f54554cad7992f512b3f29ec4"
  ],
  "id": 1
}

Errors

CodeMessageDescription
29Transaction hash not foundThe transaction does not exist or has not been processed yet

Examples

Use Cases

  • Transaction Confirmation - Verify that a submitted transaction was executed successfully
  • Fee Tracking - Record actual fees paid for cost analysis and accounting
  • Event Monitoring - Extract emitted events for token transfers, contract state changes, and DeFi activity
  • Error Debugging - Inspect revert reasons for failed transactions
  • L1 Finality Tracking - Monitor when transactions achieve ACCEPTED_ON_L1 finality via Ethereum proof verification
  • Payment Verification - Confirm token transfer completion for payment processing systems

Related Methods

  • starknet_getTransactionByHash - Get transaction details (without execution results)
  • starknet_getTransactionStatus - Get lightweight finality status
  • starknet_getEvents - Query events by filter across blocks
  • starknet_getBlockWithReceipts - Get all receipts in a block

starknet_getTransactionByHash - Get the det...

Get the details and status of a submitted transaction

starknet_getTransactionStatus - Gets the tr...

Gets the transaction status (possibly reflecting that the tx is still in the mempool, or dropped from it)

On this page

OverviewErrorsExamplesUse CasesRelated Methods