get
Returns recent transaction signatures that touched a given address, newest first.
getSignaturesForAddress walks an account's transaction history backwards from a starting point, returning matching signatures with a short status summary for each — no full transaction bodies.
getTransaction or getSignatureStatuses, paired with this call, supply full detail once specific transactions are identified.
Parameters
params is a JSON array, with values in this order: address, config.
Account address to search transaction history for, base-58 encoded.
Optional configuration.
Show propertiesProperties
Bank state to search from. processed is not accepted here.
confirmedfinalizedMinimum slot the node must have processed before answering.
Maximum number of signatures to return.
1Maximum: 1000Start searching backwards from this signature, exclusive. Omit to start from the most recent transaction.
Stop searching once this signature is reached, exclusive. Useful for paging forward to "catch up" from a previously-seen signature.
Result
An array of signature-info objects, ordered newest-first. Not wrapped in a context/value envelope.
Show each itemEach item
Transaction signature, base-58 encoded.
Slot the transaction was processed in.
Null if the transaction succeeded; a TransactionError object if it failed. Failed transactions are still included.
Contents of the transaction's memo instruction, if it had one.
Estimated production time of the containing block, as Unix seconds.
Confirmation status at the time of the response.
processedconfirmedfinalizednullNotes
- Failed transactions are included (see the third example entry, a program-defined
Customerror); theerrfield distinguishes successes from failures client-side. - Paging through history uses the last
signaturereceived asbeforeon the next call. - constant-k keeps a rolling window of ledger history; old signatures stop appearing once paging passes the retention window, whose start
minimumLedgerSlotreports.