How to Read a TON Transaction on Tonscan Step by Step

12 October 2026

You can read a TON transaction on Tonscan by entering the transaction hash or your wallet address into the search bar, then interpreting the fields on the result page. The most important information is the status, the amount and token type, the sender and receiver addresses, the fee, and the sequence of internal messages. Here is how to work through each part.

What you need before you start

You need a transaction hash (a 64-character hexadecimal string starting with a hyphen or underscore) or the address of a wallet that sent or received the transaction. You can get a hash from your wallet’s transaction history, a Telegram bot receipt, or a link someone shared. You do not need a TON wallet or any login to use Tonscan.

Step 1: Open Tonscan and Enter the Hash

Go to tonscan.org. In the search bar at the top of the page, paste the transaction hash or wallet address. Press Enter or click the search icon. If you entered a hash, you go directly to the transaction page. If you entered a wallet address, you see a list of that wallet’s transactions. Click the hash of the one you want to inspect.

Step 2: Check the Transaction Status

At the top of the transaction page, look for a colored badge.

• Green “OK” - The transaction was included in a block and executed successfully.
• Red “Failed” - The transaction was processed but the smart contract rejected it. Common reasons are insufficient balance, a failed Jetton transfer, or an exit code like 35. You still paid the fee.
• Yellow “Pending” - The transaction is in the mempool and has not been included in a block yet. If it stays pending for more than a few minutes, it may be stuck.

Below the status, you see the block height, the timestamp in UTC, and the number of confirmations. A single confirmation is usually enough for a simple transfer, but for high-value transactions you may wait for a few more.

Step 3: Identify the Sender and Receiver

Scroll to the section labeled “Accounts” or look at the row of address boxes. The sender address is on the left, the receiver address is on the right. Each address is a long string starting with “EQ” or “UQ” for standard wallets, or “Ef” for other contract types.

• If the transaction involves a Jetton transfer, you will see three addresses: the sender, the receiver, and the Jetton master contract address. The master contract is the token’s smart contract, not a person.
• If the transaction involves a DEX swap, you will see multiple internal messages and several contract addresses. The wallet you control is only one of them.

Click any address to open its wallet page, where you can see its balance and transaction history.

Step 4: Read the Amount and Token Type

Directly below the addresses, you see the transferred amount and the token symbol. For a plain TON transfer, it says something like “10 TON”. For a Jetton transfer, it says the amount and the Jetton symbol, such as “500 NOT” or “1,234.56 USD₮”.

• If the transaction is a swap, the “Value” field may show 0 TON. That is normal - the actual token movement happens inside internal messages, not in the top-level value field.
• To see the exact amount of a Jetton, look for the “Jetton Transfer” internal message in the list below the main fields. It shows the amount in the token’s native decimal places.

Step 5: Review the Fee

The fee is shown in TON, usually in a field labeled “Fee” or “Transaction Fee”. For a simple transfer, this is typically a fraction of a TON. For complex transactions like swaps or NFT purchases, the fee can be higher because multiple internal messages each cost gas.

• If you see a fee that seems high, check the number of internal messages. Each internal message adds a small cost.
• The fee is paid by the sender and is deducted from the sent amount or from the sender’s balance, depending on the wallet implementation.

Step 6: Read the Internal Messages

Below the main fields, there is a list of “Internal Messages” or “Actions”. This is where the real detail lives. Each internal message represents a step the transaction triggered inside the TON blockchain.

• Simple transfer - One internal message: the value moves from sender to receiver.
• Jetton transfer - Two internal messages: first the wallet sends Jettons to the master contract, then the master contract sends them to the receiver.
• DEX swap - Multiple internal messages: approve, transfer to pool, swap, send output tokens.
• NFT purchase - Internal messages for the sale contract, the NFT ownership transfer, and the royalty payment.

For each internal message, you can see: - The source and destination addresses. - The amount and token type. - The exit code (0 means success, anything else means that step failed).

If a transaction shows a green OK at the top but one internal message has a non-zero exit code, the overall transaction still succeeded, but that specific step failed. That sometimes happens with partial fills or expired orders.

Step 7: Check for Extra Data

Some transactions include a comment or a memo. This is visible in the “Comment” or “Payload” field. Comments are plain text sent with a transfer, often used by exchanges to identify deposits. Payloads are raw hex data sent to a smart contract. If you see a payload, the transaction is calling a specific function, not just sending tokens.

Common Pitfalls

• Don’t confuse the master contract address with the receiver address. If you see a Jetton transfer, the receiver address is the one that ends up holding the tokens, not the master contract.
• Don’t expect a “confirmed” field. TON does not use the same confirmation model as Bitcoin or Ethereum. One block inclusion is enough for finality. The “Confirmations” counter just tells you how many blocks have been built on top of that block.
• Don’t ignore failed internal messages. A transaction can appear successful at the top but still fail to deliver what you expected if one internal step returned an error code.

When to use tonscan

Use Tonscan to verify that a transaction reached its intended destination, to check whether a swap executed at the expected rate, or to debug a failed transfer. You do not need it for everyday sends if your wallet shows a clear confirmation. For any transaction that involves a smart contract, a DEX, or a Jetton, the scan page gives you the only reliable record of what actually happened.

Back to ton