GET
/
transactions
Get Transactions
curl --request GET \
  --url https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v3/transactions
{
  "transactions": [
    {
      "hash": "<string>",
      "lt": "<string>",
      "account": "<string>",
      "now": 123,
      "origStatus": "<string>",
      "endStatus": "<string>",
      "totalFees": "<string>"
    }
  ]
}
The transactions endpoint retrieves a list of transactions from the TON blockchain. This endpoint allows you to fetch recent transactions and provides options for pagination and sorting.
Get you own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
TON pricing is the same for full, archive, v2, v3There’s no difference between a full node an archive node in data availability or pricing.
All data is always available and all node requests are consumed as 1 request unit.

​
Parameters

  • limit (integer, optional) — The maximum number of transactions to return. Default: 128.
  • offset (integer, optional) — The number of transactions to skip before starting to return results. Default: 0.
  • sort (string, optional) — The sorting order of the transactions. Possible values: asc (ascending) or desc (descending). Default: desc.

​
Response

  • transactions (array) — An array of transaction objects, each containing:
    • hash (string) — The transaction hash.
    • lt (string) — The logical time of the transaction.
    • account (string) — The account address involved in the transaction.
    • now (integer) — The timestamp of the transaction.
    • origStatus (string) — The original status of the account.
    • endStatus (string) — The end status of the account.
    • totalFees (string) — The total fees for the transaction.

​
Use case

The transactions endpoint is useful for various applications that need to monitor or analyze transaction activity on the TON blockchain:
  1. Block explorers can use this to display recent transactions and allow users to browse through transaction history.
  2. Wallet applications can fetch and display recent transactions for a user’s account.
  3. Analytics tools can use this endpoint to gather data on transaction volumes, fees, and patterns over time.
  4. Monitoring systems can track specific types of transactions or activity from particular accounts.

Query Parameters

​
limit
integer
default:128

The maximum number of transactions to return

​
offset
integer
default:0

The number of transactions to skip before starting to return results

​
sort
enum<string>
default:desc

The sorting order of the transactions

Available options:
asc,
desc

Response

200 - application/json

Successful response

The response is of type object.