getmasterchaininfo - TON

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

This method returns the up-to-date state of the TON masterchain, including the latest masterchain block ID. It is the TON equivalent of asking for the current chain tip and is the recommended starting point for indexers and explorers.

Parameters

  • None

Request Example

REST (GET):

curl --location --request GET 'https://go.getblock.io/<ACCESS-TOKEN>/getMasterchainInfo' \
--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": "getMasterchainInfo",
    "params": {},
    "id": "getblock.io"
}'

Response Example

Response Parameters

Field
Type
Description

result.last.workchain

integer

Workchain ID (-1 for masterchain)

result.last.shard

string

Shard ID (-9223372036854775808 is the full shard)

result.last.seqno

integer

Sequence number of the latest masterchain block

result.last.root_hash

string

Root hash of the latest block (base64)

result.last.file_hash

string

File hash of the latest block (base64)

result.state_root_hash

string

Root hash of the masterchain state

result.init

object

Block ID of the network's init block (genesis-equivalent)

Use Cases

  • Determining the current chain tip for indexers

  • Polling for new masterchain blocks

  • Establishing a consistent read snapshot via seqno for subsequent calls

  • Health-checking the RPC endpoint

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?