trylocatetx - TON

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

This method attempts to locate the outgoing transaction at the destination address, identified by the inbound message parameters (source, destination, and creation logical time). Use it to follow the result of a sent message.

Parameters

Parameter
Type
Required
Description

source

string

Yes

Source address of the message

destination

string

Yes

Destination address of the message

created_lt

string

Yes

Creation logical time of the message (string-encoded int64)

Request Example

REST (GET):

curl --location --request GET 'https://go.getblock.io/<ACCESS-TOKEN>/tryLocateTx?source=EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2&destination=EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2&created_lt=47652103000000' \
--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": "tryLocateTx",
    "params": {
        "source": "EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2",
        "destination": "EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2",
        "created_lt": "47652103000000"
    },
    "id": "getblock.io"
}'

Response Example

Response Parameters

Field
Type
Description

result.transaction_id.lt

string

Logical time of the located transaction

result.transaction_id.hash

string

Hash of the located transaction

result.utime

integer

Unix timestamp of the transaction

result.in_msg

object

Inbound message details matching the request

Use Cases

  • Confirming that a sent message produced a destination-side transaction

  • Post-broadcast tracking after sendBoc

  • Reconstructing message → transaction lineage for analytics

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?