Skip to main content

​
getSignatureStatuses RPC Method

Returns the statuses of a list of signatures.

​
Method Information

  • Each signature must be a txid (the first signature of a transaction)
  • By default, searches only the recent status cache
  • Recent status cache retains statuses for all active slots plus MAX_RECENT_BLOCKHASHES rooted slots

​
Parameters

array required
An array of transaction signatures to confirm
  • Base-58 encoded strings
  • Maximum of 256 signatures per request
object optional
Configuration object containing the following fields:searchTransactionHistory bool optional\
  • If true - Solana node will search its ledger cache for signatures not found in the recent status cache

​
Code Sample

curl https://rpc.testnet.soo.network/rpc \
-X POST \
-H "Content-Type: application/json" \
-d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getSignatureStatuses",
  "params": [
    [
      "5ThJTCxpdn54bk3gBAWKZS4K9ogHEX56WooYbXQDnm3Q",
      "BESTc6u4kKPDrdAXHTKPgCm9bwBzDn2Nq9g4gk1Ld3P4"
    ],
    {
      "searchTransactionHistory": true
    }
  ]
}'

​
Response

{
  "jsonrpc": "2.0",
  "result": {
    "context": {
      "slot": 369624
    },
    "value": [
      {
        "slot": 369623,
        "confirmations": 1,
        "err": null,
        "confirmationStatus": "confirmed"
      },
      null
    ]
  },
  "id": 1
}

​
Result Details

An array of results, each potentially containing:
  • <null> - Unknown transaction
  • <object> - Transaction status information:
    • slot: <u64>
      • The slot where the transaction was processed
    • confirmations: <usize|null>
      • Number of blocks since signature confirmation
      • null if rooted and finalized by cluster supermajority
    • err: <object|null>
      • Transaction error details
      • null if transaction succeeded
      • Contains TransactionError details if transaction failed
    • confirmationStatus: <string|null>
      • Cluster confirmation status
      • Possible values: processed, confirmed, or finalized

​
Important Notes

  • Supports up to 256 signatures per request
  • Optional historical search available
  • Provides detailed transaction processing information