For the complete documentation index, see llms.txt. This page is also available as Markdown.

gettransactions - TON

Example code for the gettransactions JSON-RPC method. Сomplete guide on how to use gettransactions JSON-RPC in GetBlock.io Web3 documentation.

This method returns historical transactions for a given address. Pagination uses the lt (logical time) and hash cursor, with to_lt as an inclusive lower bound. Set archival=true to query historical data older than the standard retention window.

Parameters

Parameter
Type
Required
Description

address

string

Yes

Address to query

limit

integer

No

Maximum number of transactions to return (default: 10)

lt

string

No

Logical time of the transaction to start from

hash

string

No

Transaction hash to start from

to_lt

string

No

Logical time to stop at (default: 0)

archival

boolean

No

Whether to use an archival node (default: false)

Request Example

REST (GET):

curl --location --request GET 'https://go.getblock.io/<ACCESS-TOKEN>/getTransactions?address=EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2&limit=10' \
--header 'Content-Type: application/json'

JSON-RPC (POST):

curl --location --request POST 'https://go.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "getTransactions",
    "params": {
        "address": "EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2",
        "limit": 10
    },
    "id": "getblock.io"
}'

Response Example

Response Parameters

Field
Type
Description

result

array

Array of transactions, newest first

result[].utime

integer

Unix timestamp at which the transaction was applied

result[].transaction_id.lt

string

Logical time of the transaction

result[].transaction_id.hash

string

Hash of the transaction (base64)

result[].fee

string

Total fee paid (nanotons)

result[].in_msg

object

Incoming message that triggered the transaction, if any

result[].out_msgs

array

Outgoing messages sent by the transaction

Use Cases

  • Wallet transaction history views

  • Indexers and explorers per-address feeds

  • Bookkeeping and accounting systems

  • Detecting incoming Jetton or NFT transfers

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

422

Validation Error

Request parameters are missing or malformed

429

Too Many Requests

Rate limit exceeded for your plan

504

Lite Server Timeout

Upstream TON liteserver timed out

SDK Integration

Last updated

Was this helpful?