getSignaturesForAddress RPC Method
Please note that the parameter minContextSlot is not a filter on historical transactions. You can use the before or until parameter to filter historical transactions.
Parameters
account_address
string
REQUIRED
The account address encoded as base-58 string
object
object
(Optional) The configuration object with the following fields:
limit
integer
The maximum number of transaction signatures to return (between 1 and 1000). The default value is 1000
before
string
Start searching backward from this transaction signature. If not provided, the search starts from the top of the highest max confirmed block
until
string
Searches until this transaction signature, if found before limit reached
commitment
string
The level of commitment required for the query. The options include:
minContextSlot
integer
The minimum slot at which the request can be evaluated
Returns
result
A JSON object with the following fields:
blockTime
The estimated production time, as Unix timestamp (seconds since the Unix epoch). Null if not available
confirmationStatus
The transaction's cluster confirmation status. The status can either be processed, confirmed, or finalized
err
Error code if the transaction failed or null if the transaction succeeds
memo
The memo associated with the transaction and null if no memo is present
signature
The base58-encoded signature of the transaction
slot
The slot number in which the transaction was confirmed
Request
Response
Don't have an account yet?
Create your QuickNode endpoint in seconds and start building
Get started for free