get
Returns the confirmation status of up to 100 transaction signatures.
getSignatureStatuses checks whether transactions landed and how confirmed they are, without returning full transaction bodies. Pass up to 100 signatures to get each one's slot, confirmation count, status and any error, or null if the node has no record of it.
A send-and-confirm flow polls it after sendTransaction until the status is confirmed or finalized, or an error appears, instead of blocking on a subscription.
Parameters
params is a JSON array, with values in this order: signatures, config.
Up to 100 transaction signatures to check, base-58 encoded.
100Optional configuration.
Show propertiesProperties
When true, also search the node's full retained ledger history, not just its cache of recently processed signatures. Needed to get a result for anything older than the last few minutes.
Result
One status per input signature, in order, wrapped with context.
Show propertiesProperties
Show propertiesProperties
Show one ofOne of
Show propertiesProperties
Slot the transaction was processed in.
Number of blocks since confirmation, or null once the transaction is rooted/finalized.
Null on success; a TransactionError object on failure.
processedconfirmedfinalizednullDeprecated legacy field mirroring err: {"Ok": null} or {"Err": ...}.
Notes
- Maximum 100 signatures per call.
- Without
searchTransactionHistory: true, this checks only the node's short-lived recent-status cache; a valid signature older than a few minutes can come backnull. confirmations: nullmeans finalized, not unknown; a transaction carries a count only while still working toward finality.- Not available on the Free plan.