Sending 10 USDT to a friend takes a second. Then, instead of one line, the explorer shows a chain: a message to the wallet, a message to the token wallet, another to the recipient, a notification, a return of the unused fee. The transfer seems to have "smeared", although the money arrived long ago.

That is by design: it is how TON is built. The network works not like a single till where every operation joins one shared queue, but like a postal system: each contract has its own mailbox, and operations are letters between mailboxes. Understand this scheme once, and the explorer starts making sense.

~0.4 seconds
The interval between TON mainnet blocks since April 2026.
~1 second
Time to finality after the consensus upgrade.
2 workchains
In operation now: the masterchain and the basechain.

The main idea

A postal network

In many blockchains every operation joins one shared queue and runs in order. TON is built differently: each account is a smart contract with its own state, and contracts talk through messages. Once a message is sent, it goes, and the sender does not wait for the recipient to process it.

That is why the network can be divided into parts that work in parallel. And any complex operation — a token swap, an NFT purchase, a USDT transfer — becomes a chain of letters between contracts.

Terms

Glossary

Term

What it is

Analogy

Masterchain

The chain with network settings and system contracts that records the state of the other parts

Head post office

Workchain

A separate blockchain with its own rules. There are two now: the masterchain (number −1) and the basechain (number 0)

A postal system

Shardchain

A part of the basechain. It splits and merges depending on load

A district branch

Smart contract

Any account, your wallet included: code plus state

A mailbox with its own rules

Message

External — from the outside world to a contract; internal — from contract to contract

A letter

Transaction

A record of a contract's state change while processing a message

An entry in the branch's log

Trace

All messages and transactions caused by one operation

All the correspondence on one case

Validators

Nodes that stake GRAM to produce and confirm blocks

Postal inspectors

Shards

How the network shares the load

The basechain can start as a single shardchain. When the number of operations per block exceeds a threshold, validators split it in half: accounts are divided between two shards according to the beginning of their address. When the load falls, the shards merge again. The number of shards is always a power of two and can vary from one to two to the sixtieth power.

Shards exchange messages directly using a "hypercube" scheme: each shard has a limited circle of neighbours, and a letter arrives after a few hops. If a shard is overloaded, messages that did not fit into the current block are processed in the following ones.

Users never need to choose a shard: it is determined by the address automatically.

One shard splits into two; the shards exchange messages and can merge again.
Read from left to right. Higher load causes a split; lower load allows a merge, shown dashed. Arrows between shards represent messages.

Asynchrony

Why a transfer is a chain

An ordinary GRAM transfer looks like this. Your app sends your wallet an external message with a signature. The wallet checks the signature, records a transaction and sends an internal message to the recipient. The recipient's contract processes it in its own transaction. Two transactions in two contracts, possibly in different shards and blocks.

With tokens there are more steps. Your wallet writes to your token wallet, that writes to the recipient's token wallet, and that one notifies the recipient and returns the unused part of the fee to you. Each step is a separate transaction, and they finish at different times.

So the green status of the first transaction is not the outcome yet. Check whether the last step went through. How to read such a chain in an explorer is covered in "How to read a TON transaction in an explorer: a receipt nobody can fake".

Bounce. If the recipient's contract fails to process a message, and the message carries the bounce flag, the network sends the money back to the sender minus fees. That is what TON's two address formats are about: "bounceable" and "non-bounceable". Why this matters is covered in "TON addresses: why they start with UQ or EQ".

Validators

Who confirms the blocks

Blocks are produced and confirmed by validators — nodes whose owners stake large amounts of GRAM. The validator set is chosen in elections run by system contracts on the masterchain, and a validator that breaks the rules risks its stake. Ordinary users can take part indirectly, through staking.

In 2026 the consensus was upgraded to Catchain 2.0. Since 9 April 2026, mainnet blocks come about every 0.4 seconds instead of 2.5, and an operation becomes final in about a second instead of ten. If an app still shows a delay of ten seconds or so, the cause may not be the network but how the app learns about the result.

In practice

What this means for you

  • Fast, but not instant everywhere. The network confirms operations in about a second, while multi-step operations finish when the last step goes through.
  • Check the outcome, not the first step. For a swap, an NFT purchase or a pool withdrawal, what matters is the result of the whole chain.
  • The fee depends on how the operation is built. The more steps and computation, the higher it is, and the excess may come back. More in "TON fees: what GRAM pays for and why some of it comes back".
  • Contracts pay for storage. Keep at least a little GRAM in your wallet: an account with accumulated storage debt can be frozen.

Questions

How many operations per second can TON handle?

In a public test on 31 October 2023 the network reached 100,000 transactions per second, according to the TON docs. That is how the network performed in a test, while real throughput depends on how many people are using the network.

Why does a transfer "hang" in the app if the network is so fast?

The app may learn about the status with a delay, and a multi-step operation waits for its last step. Open the transfer in an explorer: if every step has gone through, the money is there, however long the spinner turns.

How does TON differ from other blockchains in practice?

In its address format, fee coin, transfer comments and where its apps live. A comparison with Ethereum, Solana and TRON is in "TON, Ethereum, Solana and TRON: how the TON network differs".


TON is a postal network of many branches that split and merge with the load. Contracts correspond through messages, which is why the network is fast, and why every complex operation shows up in an explorer as an exchange of several letters.

Users need to remember just two consequences: an operation's outcome is read from its last step, and a refund on error is a normal part of the scheme. The network does the rest.