GET
/
getTransactions
curl --request GET \
  --url https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v2/getTransactions
[
  {
    "transaction_id": {
      "lt": "<string>",
      "hash": "<string>"
    },
    "utime": 123,
    "fee": "<string>",
    "storage_fee": "<string>",
    "other_fee": "<string>",
    "transaction_type": "<string>",
    "compute": {},
    "action": {},
    "in_msg": {},
    "out_msgs": [
      "<any>"
    ]
  }
]

The getTransactions method retrieves the transaction history for a specific address on the TON blockchain. This method allows you to fetch a list of transactions associated with an address, with options to limit the number of results and specify the starting point of the search.

Get you own node endpoint today

Start 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, v3

There’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.

​
JSON-RPC example

Shell
curl -X POST \

  'https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v2/jsonRPC' \

  -H 'Content-Type: application/json' \

  -d '{

    "jsonrpc": "2.0",

    "id": 1,

    "method": "getTransactions",

    "params": {

      "address": "EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2",

      "limit": 10,

      "to_lt": 0,

      "archival": false

    }

  }'

​
Parameters

  • address (string, required) — The address for which to retrieve transactions. Example: EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2.
  • limit (integer, optional) — The maximum number of transactions to return. Default: 10.
  • to_lt (integer, optional) — The logical time to start the search from (0 means from the latest). Default: 0.
  • archival (boolean, optional) — Whether to use an archival node for the query. Default: false.

​
Response

An array of transaction objects, each containing:

  • transaction_id (object) — The unique identifier of the transaction, containing:
    • lt (string) — The logical time of the transaction.
    • hash (string) — The hash of the transaction.
  • utime (integer) — Unix timestamp of the transaction.
  • fee (string) — The fee for the transaction in nanotons.
  • storage_fee (string) — The storage fee for the transaction in nanotons.
  • other_fee (string) — Other fees for the transaction in nanotons.
  • transaction_type (string) — The type of the transaction.
  • compute (object) — Computation details of the transaction.
  • action (object) — Action details of the transaction.
  • in_msg (object) — Details of the incoming message.
  • out_msgs (array) — Details of the outgoing messages.

​
Use case

A possible use case for the getTransactions method in TON is for blockchain explorers or wallet applications that need to display transaction history for a specific address. This method can be used to show recent transactions, calculate total incoming/outgoing amounts, or analyze transaction patterns for a given address.

Query Parameters

​
address
string
default:EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2
required

The address to get transactions for

​
limit
integer
default:10

The maximum number of transactions to return

​
to_lt
integer
default:0

The logical time to start the search from (0 means from the latest)

​
archival
boolean
default:false

Whether to use archival node for the query

Response

200 - application/json
Transaction history for the specified address
​
transaction_id
object
​
utime
integer

Unix timestamp of the transaction

​
fee
string

The fee for the transaction in nanotons

​
storage_fee
string

The storage fee for the transaction in nanotons

​
other_fee
string

Other fees for the transaction in nanotons

​
transaction_type
string

The type of the transaction

​
compute
object

Computation details of the transaction

​
action
object

Action details of the transaction

​
in_msg
object

Details of the incoming message

​
out_msgs
any[]

Details of the outgoing messages