Transaction
getTransactionsForAddress
Transaction history query with advanced filtering, bidirectional sorting, and efficient pagination. This method provides significantly more power than the standard getSignaturesForAddress, with features including: • Retrieve full transaction data in a single call without additional getTransaction requests • Time-based filtering with Unix timestamps and slot ranges • Status filtering for succeeded/failed transactions • Chronological or reverse-chronological sorting • Simple pagination with slot:position tokens.
Parameters
addressstring required Base-58 encoded public key of the account to query transaction history for.
configobject optional Configuration object with advanced filtering options.
transactionDetailsstringLevel of detail to return: "signatures" for basic info (up to 1000), or "full" for complete transaction data (up to 100). Default: "signatures".
sortOrderstringSort order: "desc" for newest first (default), or "asc" for chronological order (oldest first).
limitnumberMaximum transactions to return. Up to 1000 for "signatures" mode, up to 100 for "full" mode.
paginationTokenstringPagination token from previous response in format "slot:position".
commitmentstringCommitment level: "finalized" or "confirmed". Note: "processed" is not supported.
encodingstringEncoding format for transaction data (only applies when transactionDetails is "full"). Options: "json", "jsonParsed", "base64", "base58". Default: "json".
maxSupportedTransactionVersionnumberHighest transaction version to return. Set to 1 to include v1 transactions. If omitted, only legacy transactions are returned.
minContextSlotnumberThe minimum slot that the request can be evaluated at.
filtersobjectAdvanced filtering options for narrowing results.
Result
objectObject containing data array and optional paginationToken for next page.
dataarrayArray of transaction data. Structure depends on transactionDetails parameter.
paginationTokenstring | nullToken for fetching the next page in format 'slot:position', or null if no more results. Pass this value as the paginationToken parameter in the next request to continue pagination.
Solana
As we do not yet have historical data available on Solana, if a transaction is not found, we will return an error object that contains our oldest stored slot.
FOGO Mainnet
Historical data is stored for Fogo Mainnet (not Testnet). If transaction not found, result is null. Otherwise, the response returned is as below.
Example
curl "https://eu.fluxrpc.com?key=<your-API-key>" -s -X POST -H "Content-Type: application/json" -d '
{
"jsonrpc": "2.0",
"id": 1,
"method": "getTransactionsForAddress",
"params": [
"7UX2i7SucgLMQcfZ75s3VXmZZY4YRUyJN9X1RgfMoDUi",
{
"transactionDetails": "full",
"sortOrder": "asc",
"limit": 10,
"commitment": "finalized",
"filters": {
"blockTime": {
"gte": 1735689600,
"lte": 1738368000
},
"status": "succeeded",
"tokenAccounts": "balanceChanged"
},
"encoding": "jsonParsed",
"maxSupportedTransactionVersion": 1
}
]
}'