Check transaction status

Query the confirmation status of one or more blockchain transactions.
Essential for tracking transaction lifecycle and ensuring successful execution.

⚠️ ENCRYPTION REQUIRED

This endpoint requires AES-256-GCM encrypted request bodies.

All requests must be encrypted using your API credential's encryption key.
See the Request Encryption section in the Transactions tag description above for implementation details.

Request Headers:

Content-Type: text/plain
X-Encrypted: true

Response Headers:

  • X-Server-Signature: HMAC-SHA256 signature of response body (verify this!)

Usage Notes

  • Supports batch status checks for up to 100 transactions per request
  • Returns current status for each transaction hash/signature
  • Status is fetched directly from blockchain nodes
  • Results include error messages for failed transactions
  • Transaction finality varies by blockchain (instant to several minutes)
  • Repeated status checks for the same transaction consume CU

Accessibility

Tier Access: Starter, Pro, Enterprise

Compute Unit Cost: 10 CU per request

Chain Supported

ChainSupported DEXs
SolanaPump.fun, PumpAMM, Raydium (CLMM, CPMM, V4), Jupiter
EthereumUniswap V2, Uniswap V3
BaseUniswap V2, Uniswap V3
BSCFourmeme, PancakeSwap V2

Transaction Status Values

StatusDescriptionFinal?
pendingSubmitted to network, not yet processedNo
processedIncluded in a block (Solana-specific)No
confirmedConfirmed with minimum confirmationsNo
finalizedIrreversibly confirmed (highest security)✅ Yes
failedTransaction failed (check err field)✅ Yes

Note: Status progression varies by blockchain:

  • Solana: pending → processed → confirmed → finalized
  • EVM chains: pending → confirmed → finalized

Common Use Cases

  • Monitor transaction confirmation after submission
  • Implement transaction tracking in user interfaces
  • Verify successful swap execution
  • Reconcile transaction outcomes for accounting
  • Trigger actions upon transaction confirmation
  • Build transaction history dashboards
  • Implement webhook-style notifications

Best Practices

  • Always encrypt requests - Unencrypted requests will be rejected
  • Verify response signatures - Check X-Server-Signature header
  • Poll status with exponential backoff to avoid rate limits
  • Cache confirmed/finalized transaction statuses
  • Handle all possible status values in your application logic
  • For Solana: wait for "finalized" status for maximum security
  • For Ethereum/EVM: wait for 12-15 confirmation blocks
  • Implement timeout logic for stuck transactions
  • Store error messages for debugging failed transactions

Polling Recommendations

┌─────────────────────────────────────────────────────────────┐
│  Recommended Polling Strategy (Exponential Backoff)         │
├─────────────────────────────────────────────────────────────┤
│  Attempt 1:  Wait 2 seconds                                 │
│  Attempt 2:  Wait 4 seconds                                 │
│  Attempt 3:  Wait 8 seconds                                 │
│  Attempt 4:  Wait 15 seconds                                │
│  Attempt 5+: Wait 30 seconds (max interval)                 │
│                                                             │
│  Timeout: Stop after 2-5 minutes (chain-dependent)          │
│  - Solana: ~2 minutes (fast finality)                       │
│  - EVM chains: ~5 minutes (12-15 blocks)                    │
└─────────────────────────────────────────────────────────────┘
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Transaction hashes/signatures to check status for

Request to check status of one or more transactions

hashes
array of strings
required
length between 1 and 100

Array of transaction hashes or signatures to check.

Format depends on blockchain:

  • Solana: Base58-encoded signature
  • Ethereum: 0x-prefixed transaction hash
  • Other EVMs: Chain-specific hash format

Maximum: 100 hashes per request

hashes*
string
required

Blockchain network where transactions were submitted.
Must match the chain where transactions actually exist.

Responses

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json