TON Guide

The masterchain holds global configuration and references shardchain states. Most user accounts live in the basechain, which can be divided into shards. A block is identified by its workchain, shard and sequence number together; a sequence number alone is not a network-wide block height.

The top strip shows basechain blocks. Open the search menu and choose Masterchain under SELECTED to view masterchain blocks. Choose a shard when several are active. Open a block to inspect its transactions; masterchain blocks also link their referenced shards.

A transaction records one account processing a message or a system operation. Messages connect accounts; processing an incoming message may create outgoing messages and further transactions. A trace follows those linked transactions.

Use the transaction page for local execution, messages for transfers between contracts, and the trace for the wider operation. TON fundamentals.

Logical time (LT) orders transactions and messages. It is separate from the Unix timestamp shown as the transaction date. Account history uses LT as its pagination cursor; preserve it as an exact integer string.

Execution can include storage, credit, compute, action and bounce phases. The transaction page shows total fees and the recorded phase details, including gas use, forwarding costs and exit codes. A failed operation can still pay fees.

GRAM is TON’s native currency and uses 9 decimal places: 1 GRAM = 1,000,000,000 nanograms. A message value and the transaction fee describe different amounts.

A bounced message returns a response when a bounceable message cannot be processed under the applicable rules. It is a separate message with its own value and costs. Check the transaction result, compute and action results, and outgoing messages together.

A confirmed transaction can have failed execution. One successful transaction also does not establish that every later transaction in its trace succeeded. TON blockchain specification.

Confirmation means the transaction is included in its block. A multi-contract operation can involve additional transactions and messages. Inspect the full trace and final recipient rather than treating the first transaction as the whole transfer.

Accounts show their GRAM balance, state, last activity and detected contract interfaces. History groups recognized actions; Transactions lists account transactions. Jettons and NFTs have separate tabs.

The Contract tab contains state, code and data, read-only methods, and available staking, multisig, subscription and DeFi records. Expand Account details for additional fields and extra currencies.

TON accounts can be written as a raw workchain and hexadecimal account ID or a user-friendly address. Bounceability and network flags can change the user-friendly representation without changing the underlying account.

Search accepts TON addresses and .ton names. DNS resolution links to the resolved account; a domain name is not a substitute for checking the account address.

Select a listed getter in the Contract tab and supply its arguments when needed. Reads return a result without signing a transaction. Arguments may be comma-separated strings or a JSON array of strings; preserve large integers as strings.

Account details preserve code, data and storage fields. Inspection shows recognized interfaces and available compiler information.

The validators page shows the election timestamps, total and minimum stake, and participating validator accounts, stakes and ADNL addresses. These fields describe the displayed election data; an address holding stake is not automatically the producer of a particular block.

A jetton has a master contract and individual jetton-wallet contracts for holders. Identify it by the master address, not its name or symbol. The jetton page shows supply, decimals, administration and holders.

Display balances using the jetton’s own decimals. Do not assume every jetton has 9 decimals. Jetton standard.

Some jettons use a display multiplier. Current wallet balances, holder balances and total supply apply that ratio with exact rounding, then the token’s decimals. Expand Amount details to see the on-chain amount, raw units and ratio.

Historical transfers retain their recorded on-chain quantity; a current multiplier is not evidence of the multiplier at that time. Scaled UI jetton standard.

The NFT item’s contract address is its identity. Its collection, owner and item index are separate fields. Collection membership verification checks the item’s relationship to a collection; it does not establish that its image, name or seller is trustworthy.

Item details show the exact index when confirmed by the NFT contract. A display number in an NFT’s name need not equal its on-chain index.

TEP-64 supports on-chain, off-chain and combined metadata. The NFT page displays names, descriptions, images and attributes, with the full metadata available to expand. Media or metadata hosted elsewhere can change or become unavailable.

Open animations explicitly from the item page. Missing media does not erase the NFT’s contract or ownership record. Token metadata standard.

A listed NFT may be held by a marketplace sale contract. Wallet NFT lists include recognized indirect sale ownership. The item page separates the on-chain owner, seller, sale contract and price currency.

A sale listing is not a completed transfer. Use transfer history to follow changes, and the collection page to browse its items.

No. A gift must exist as a TON NFT to have an on-chain item address and ownership record here. Telegram gifts, collectible usernames and numbers can have associated TON NFTs, but a Telegram profile or ordinary username alone does not prove wallet ownership.

A collectible may be displayed on a Telegram profile while its owner remains a TON wallet. Check its item address, collection and current owner. Telegram collectible gifts.

Use Load more below the NFT list to continue through the collection or wallet. The NFTs tab includes each returned item separately, with its full name and link to item details. A wallet’s NFT collection and its transaction history are independent lists.

Collection membership, trust classification and marketplace approvals are distinct facts. Recognized names and images are not ownership proofs. Compare contract addresses and collection links before treating two similarly named assets as the same token.

Paste an address, transaction hash, message hash, block number or .ton name into search. Automatic Routing lets the taxi find its chain. Choosing a native explorer keeps that chain’s search available; View Hub returns to tx.taxi.

The last available data remains visible while fresh updates are delayed. Retry an unavailable section to load it again. An empty list and an unavailable list are different states.

tx.taxi displays public chain data. It cannot sign transactions, access private keys or reverse a transfer. For wallet or exchange account support, contact the service that submitted the operation.