How to check a TON transaction: status, fee and messages
Paste the transaction hash into the search bar on the Tongram home page and press Enter. The transaction view opens with a status label, Executed or Failed, the amount moved, the date and time, and the hash itself.
Below that you see the account the transaction belongs to, the incoming value, the outgoing value with the number of outgoing messages, the fee in GRAM, the block reference and the logical time (LT). A non-zero exit code and a text comment appear only when the transaction has them.
All of this is read from Toncenter, a public TON indexer. Tongram displays what the indexer returns and does not add its own judgement about the transfer.
What this covers
- This guide covers looking up one transaction by its hash in the Tongram explorer on TON mainnet.
- You do not need a wallet, an account or a connection to do this.
- It does not cover following a transfer across several contracts; each hop is a separate transaction in TON and is checked separately.
Steps in Tongram
- Open the Tongram home page. The search bar is at the top.
- Paste the transaction hash. Tongram recognises a 64-character hexadecimal hash or a 44-character base64 hash.
- Press Enter or tap Search. The URL changes to the transaction, so you can copy the link or reload the page later.
- Read the status label on the card: Executed or Failed. Below it are the amount, the date and the hash with a copy button.
- Read the lines Account, In, Out, Fee, Block and LT. Exit code and Note appear only when present.
- Scroll to Messages. Each row is one incoming or outgoing message with the peer address, the opcode, a bounced mark where the indexer sets one, and the value carried.
- Tap a message row to open the peer account, or tap Open account to see the account the transaction belongs to.
What you see and where it comes from
- Status, fee, messages, block and LT come from the Toncenter v3 /transactions endpoint. Tongram sends only the hash you typed.
- Executed means the indexer reported no failure in the compute and action phases and the transaction was not aborted. Any of those failing is shown as Failed.
- The Fee line is the total_fees field of the transaction record, shown in GRAM with nine decimals. It is the fee charged to this account for this transaction, not the sum of fees along a multi-hop transfer.
- The text comment is decoded by the indexer from the incoming message body. Opcodes are shown as the indexer reports them.
- The amount on the card is the incoming value when there is one, otherwise the sum of outgoing values. This is a display choice, not a chain field.
Freshness and limits
- A transaction that was just sent may not be indexed yet. "Transaction not found" can mean not yet indexed, not only non-existent; try again in a moment.
- One hash identifies one transaction on one account. A transfer between two wallets produces at least two transactions, and the recipient side has its own hash.
- Tongram does not compute a success or failure judgement of its own beyond the indexer fields listed above. What happened inside a contract is not interpreted.
- If Toncenter is unavailable, the view reports the error rather than showing older data.
Common mistakes
- Searching a message hash instead of a transaction hash. Wallet apps sometimes show the hash of the external message, which is a different value.
- Reading Executed as "the recipient got the money". It means this account processed the transaction; the receiving side is a separate transaction.
- Reading the fee as the network-wide cost of the transfer. Fees on other hops appear on their own transactions.
- Resending a transfer because the hash was not found yet. Check again first; two sends produce two transfers.