getTransactionsForAddress — Solana JSON-RPC

getTransactionsForAddress returns the transactions that reference an address, in the order you choose. Set sortOrder to asc to start from the very first transaction the address ever made, or to desc for the most recent ones. Each page holds up to 1000 entries — either signature summaries or complete transactions with meta — and carries a paginationToken for the next page.

It replaces the usual two-step history scan. With the standard methods you page backwards through getSignaturesForAddress from the newest signature and then call getTransaction for each one; reaching an old wallet's first transaction means walking its entire history. Here one ascending call returns that first transaction directly, and transactionDetails: "full" returns the transactions themselves.

Filters narrow the history server-side: a slot or block-time window, only succeeded or only failed transactions, and optionally the activity of token accounts owned by the address.

The method is a heavy read (sol_read_rpc_heavy) and shares that budget with getProgramAccounts — 2 rps on the Free trial, rising to 80 rps on business.

Positional params array: [address, config?].

The result is one page: a data array and the cursor for the next page. Response to the request above — the address's first two transactions, from January 2022:

With transactionDetails: "full" each data entry is a complete transaction instead — the same shape getTransaction returns, plus the position of the transaction in its block:

{
  "slot": 116982180,
  "blockTime": 1642623466,
  "transactionIndex": 280,
  "version": "legacy",
  "transaction": {
    "signatures": ["6HtVDabXRSxYeQ6ennJ8rqTfs8oLFKViSv275SMaasoqNUke1VbAHLzmq41KQ1qYSvZxeL84tVQWDX8XcuBft1A"],
    "message": { "accountKeys": ["..."], "header": { "...": "..." }, "instructions": ["..."], "recentBlockhash": "..." }
  },
  "meta": { "err": null, "fee": 5000, "preBalances": ["..."], "postBalances": ["..."], "logMessages": ["..."], "...": "..." }
}

Errors use the standard JSON-RPC envelope (error.code, error.message, error.data).

See the shared errors reference for the full envelope and retry guidance.

JavaScript (fetch)

// Replay a wallet's history from its first transaction, page by page.
// Stay under your heavy-read RPS between pages.
async function page(paginationToken) {
  const res = await fetch("https://triport.io/sol", {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${process.env.TRIPORT_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      jsonrpc: "2.0",
      id: 1,
      method: "getTransactionsForAddress",
      params: [
        "86xCnPeV69n6t3DnyGvkKobf9FdN2H9oiVDdaMpo2MMY",
        {
          transactionDetails: "signatures",
          sortOrder: "asc",
          limit: 1000,
          filters: { status: "succeeded" },
          ...(paginationToken ? { paginationToken } : {}),
        },
      ],
    }),
  });
  const { result, error } = await res.json();
  if (error) throw new Error(`${error.code}: ${error.message}`);
  return result;
}


let token;
do {
  const { data, paginationToken } = await page(token);
  for (const tx of data) console.log(tx.slot, tx.signature);
  token = paginationToken; // null once the history is exhausted
} while (token);

Python (requests)

import os
import time


import requests


# Transactions of the last 24 hours, newest first, with full details.
since = int(time.time()) - 86400
payload = {
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getTransactionsForAddress",
    "params": [
        "86xCnPeV69n6t3DnyGvkKobf9FdN2H9oiVDdaMpo2MMY",
        {
            "transactionDetails": "full",
            "sortOrder": "desc",
            "limit": 100,
            "maxSupportedTransactionVersion": 0,
            "filters": {"blockTime": {"gte": since}},
        },
    ],
}
r = requests.post(
    "https://triport.io/sol",
    json=payload,
    headers={"Authorization": f"Bearer {os.environ['TRIPORT_API_KEY']}"},
    timeout=60,
)
for tx in r.json()["result"]["data"]:
    print(tx["slot"], tx["transaction"]["signatures"][0], tx["meta"]["err"])

• Order. asc walks forward from the address's first transaction — the way to backfill a wallet or find when it was created. desc matches the order of getSignaturesForAddress.
• Paging. Send the returned paginationToken back unchanged with the same address and options, and stop when it comes back null. A page shorter than limit does not mean the end — the final call may return an empty data array with paginationToken: null. Each page is a separate heavy read and counts against your RPS budget.
• Page size. Up to 1000 entries in both modes. A page of 1000 full transactions can be several megabytes; lower limit if you parse responses in a memory-constrained process.
• Commitment. Only confirmed and finalized are accepted.
• Heavy rate limits. getTransactionsForAddress shares the sol_read_rpc_heavy budget — 2 / 5 / 20 / 80 rps by tier; see rate limits and tiers.
• Related methods: getSignaturesForAddress (standard newest-first signature scan), getTransaction (single transaction by signature), and signatureSubscribe (stream the confirmation of a new signature).