TON / block
TON block lookup
Look up any TON block on Tonviewer. tx.taxi detects the format, picks the right TON explorer, and redirects.
TON (The Open Network) uses a workchain-and-shard architecture rather than a single linear chain, and its addresses look nothing like an Ethereum hex string. A user-friendly TON address is a 48-character base64url-encoded value, often starting with EQ or UQ, that encodes the workchain, account ID, and flags. Transactions are referenced by a logical time plus account or by message hash on most explorers. Paste a TON address or transaction reference at tx.taxi/{value} and the router classifies the TON format and 302-redirects you straight to Tonviewer's account or transaction page, so you skip the chain picker. On this page: TON block lookups specifically.
How it works
- Copy your
TON block(e.g. a block height or hash). - Paste into the search above or visit
tx.taxi/<your-block>directly. - tx.taxi detects the TON format and redirects to Tonviewer.
Frequently asked questions
What does a TON address look like?
A user-friendly TON address is 48 base64url characters, often starting with EQ (bounceable) or UQ (non-bounceable). The same account can also be written in raw form as workchain:account-id, like 0:abcd... with a 64 hex character account ID.
Why are there two formats for the same TON address?
TON addresses encode flags including a 'bounceable' bit that controls how messages behave if the destination contract does not exist. EQ-prefixed addresses are bounceable, UQ-prefixed are non-bounceable, but both refer to the same underlying account.
How do TON transactions differ from Ethereum?
TON does not have a single global transaction list. Transactions are tied to specific accounts and shards, and are typically located by logical time plus account hash or by message hash. Tonviewer normalises these lookups into a single tx page.