Skip to main content
GET
Get a transaction's status

Authorizations

X-API-Key
string
header
required

Path Parameters

signature
string
required

Signature returned when the transaction was sent.

Response

Current status.

commitment
enum<string>
required

The commitment requested when it was sent.

Available options:
processed,
confirmed,
finalized
err
any | null
required

On-chain execution error when status is failed, as Solana RPC returns it: a string (e.g. "InsufficientFundsForRent") or an object (e.g. {"InstructionError": [0, {"Custom": 1}]}).

landedAt
integer<int64> | null
required

When the relay saw it reach commitment (Unix ms).

landingMs
integer<int64> | null
required

landedAt - receivedAt. Includes up to ~400 ms of status-polling delay.

reason
object | null
required

Why it failed or expired; null while pending and when landed. For failed, the relay refines it with the transaction's on-chain logs a second or two after landing.

receivedAt
integer<int64>
required

When the relay received it (Unix ms).

rpcError
string | null
required

Last error from the staked RPC send, if any. Informational: the transaction is still sent directly to leaders.

sends
integer
required

Times the relay has sent it (first send plus re-sends, at most 1 + maxRetries).

signature
string
required
slot
integer<int64> | null
required

Slot it landed in.

status
enum<string>
required
  • pending: being sent; not yet seen at commitment.
  • landed: reached commitment and executed successfully.
  • failed: reached commitment but execution failed; fees were paid. See reason (and the raw err).
  • expired: the blockhash expired before the transaction landed. It can no longer land; re-sign with a new blockhash. See reason.
Available options:
pending,
landed,
failed,
expired