getAddressInformation | TON v2

The getAddressInformation method retrieves information about a specific address on the TON blockchain. This includes details such as the balance, state, code, and data associated with the address, as well as the last transaction ID.

👍

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.


Parameters

  • address (string, required) — The address for which information is being requested. Example: EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2.

JSON-RPC example

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": "getAddressInformation",
    "params": {
      "address": "EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2"
    }
  }'

Response

  • balance (string) — The balance of the address.
  • state (string) — The state of the address.
  • code (string) — The code of the address.
  • data (string) — The data of the address.
  • last_transaction_id (object) — The last transaction ID, containing:
    • lt (string) — The logical time of the last transaction.
    • hash (string) — The hash of the last transaction.
  • error (object) — Error information, if any.
  • id (integer) — The request ID.

Use case

A possible use case for the getAddressInformation method in TON is for applications that need to display or utilize the current state and balance of a specific address. For example, a wallet application may use this method to show the user's balance and transaction history.

Try the getAddressInformation RPC method yourself

Language
Click Try It! to start a request and see the response here!