Returns transaction history for an account. Transactions are returned newest-first. Each transaction shows the incoming message that triggered it, all outgoing messages, and fees paid. For pagination: use the lt and hash from the oldest transaction as the starting point for the next request.
The account address to query.
Account address in raw format (e.g., 0:ca6e321c...) or user-friendly format (e.g., EQDKbjIcfM...). All formats are automatically detected.
Maximum number of transactions to return. The default is 10. For accounts with many transactions, use pagination (lt + hash) to fetch more.
Starting point for transaction history. Pass the lt from last_transaction_id to start from the most recent, or from a specific transaction to continue pagination.
SHA-256 transaction hash to start pagination from A 256-bit hash value. Accepts either hex format (64 characters) or base64 format (44 characters). Used for block hashes, transaction hashes, and cryptographic proofs.
Stop fetching when reaching this logical time. Use this to limit the time range of returned transactions. Set to 0 (default) to fetch all available history.
Request data from archival nodes. Regular nodes keep at least the last 2 days of history. Set to true when querying old transactions or historical state. Archival requests may be slower.
Returns a list of transactions for the specified account, ordered by logical time.
Returns true if the request succeeded; otherwise false. See the error field for details.
Array of transaction objects, ordered newest-first. Each transaction contains the triggering inbound message, all outbound messages, fees in nanotons, timestamps, and the raw BOC (base64).
Optional request ID that you can pass in the request and receive back in the response. Useful for matching async responses.