Status

Status confirms whether a transaction was included in a block and whether it executed successfully, using queries, subscriptions, or Webhook. You can retrieve a receipt by transaction hash, query multiple transactions at once by block, and trace the execution path of failed transactions.

A transaction included in a block can still revert during execution. In that case no assets move and only gas is consumed. Distinguishing block inclusion from execution success with the receipt status field lets you decide accurately whether to mark a withdrawal as completed or failed.

Use Cases

  • Withdrawal OpsComplete withdrawals

    Confirm execution success with the receipt `status` field, then mark the withdrawal as completed. This prevents reverted withdrawals from being recorded as successful when you rely on block inclusion alone.

  • Service OpsExplain failure causes

    Trace the execution path of a failed transaction to find where the revert occurred. Use the cause to respond accurately to customer inquiries.

  • EngineeringBulk withdrawal status checks

    Check the status of many withdrawals at once with multi-transaction queries, block-level queries, or Webhook instead of per-transaction lookups. This significantly reduces call volume compared with per-transaction queries.

Available APIs

Transaction Queries — RPC

Transaction Queries — Data API

Subscriptions and Delivery

Execution Tracing