getSignaturesForAddress
Explore getSignaturesForAddress: Use Cases, Code Examples, Request Parameters, Response Structure, and Expert Tips
The getSignaturesForAddress RPC method retrieves a list of confirmed transaction signatures involving a specific account, ordered newest first. It’s the primary way to fetch an account’s transaction history on Solana.
✅ Common Use Cases
Wallet History Display recent transactions for a user’s wallet. For richer parsing, consider CoinVera’s Enhanced Transactions API.
Activity Auditing Review all transactions tied to a particular smart contract or account.
Targeted Lookup Locate a specific transaction when you only know the involved address.
Local Indexing Build a custom transaction index for faster queries and analytics.
🛠 Request Parameters
{
"address": "<base58AccountPubkey>", // Required
"options": { // Optional
"limit": <number>, // 1–1000 (default 1000)
"before": "<signature>", // Fetch signatures before this one
"until": "<signature>", // Stop when this signature is reached (exclusive)
"commitment": "processed|confirmed|finalized",
"minContextSlot": <u64>
}
}address: Base‑58 public key of the target account.
limit: Max signatures to return (default and max: 1000).
before / until: Paginate by signature.
commitment: Confirmation level (defaults to the node’s setting).
minContextSlot: Minimum slot the node must have processed to serve this request.
📦 Response Structure
Returns an array of objects—each representing one signature:
signature
string
Base‑58 transaction signature
slot
u64
Slot in which the transaction was processed
err
object | null
Error details if the transaction failed
memo
string | null
Memo attached to the transaction, if any
blockTime
i64 | null
Unix timestamp of the block (seconds since epoch)
confirmationStatus
string | null
“processed”, “confirmed”, or “finalized” (may be null)
💡 Examples
Fetch the Latest Signatures Retrieve up to 1,000 newest signatures for an address.
Limit the Number of Signatures Request a specific count (e.g., 100) by setting
limit: 100.Paginate Through History Use
beforewith the last signature of the previous batch to page backwards.
Code Examples
Example Response
🧠 Developer Tips
Pagination Is Essential To walk an active account’s full history, repeat calls using
beforeand adjustlimit.Watch Rate Limits Large or frequent history queries can hit RPC provider limits.
Ordering Guaranteed Results always flow from newest to oldest.
Use
untilto Stop Early If you only need transactions up to a known signature, specifyuntilto halt the scan.Context Slot Doesn’t Filter
minContextSlotsets the node’s ledger state threshold, not a transaction filter.Full Details via
getTransactionThis method returns only signatures and metadata; retrieve full transaction info by feeding each signature intogetTransaction.
By leveraging getSignaturesForAddress with its pagination and filtering options, you can efficiently access and manage any Solana account’s transaction history.
Last updated