Transaction, Message, and Trace Differences
Tracing activity on TON requires distinguishing between transactions, messages, and traces. A transaction is any on-chain event recorded by a smart contract, but this does not itself prove that assets reached the intended address. Each transaction can generate multiple messages, which might represent jetton transfers, payments, contract calls, or system events. Analyzing these message flows is essential to determine if the transfer actually completed, rather than assuming success based on wallet interface status.
TON Center API v3 allows for programmatic access to transaction, message, account, and trace details. This deeper access helps uncover edge cases such as pending, bounced, or partial transfers, which typical wallet history views may not reveal. Confirmations require following the message path, checking delivery status, and, with tokens, inspecting the relevant token master contract state for actual receipt.
Explorer interfaces and API responses do not confirm recipient wallet ownership. Addresses shown in explorer outputs are resolved strictly from blockchain state and offer no off-chain identity guarantees. Pending, failed, or partial records should never be taken as proof of completed transfers until all trace records and account balances show settled delivery.
Checklist for Verifying Transfers
To confirm any TON or jetton transfer, do not rely solely on your wallet's transaction history. The TON Center API v3 enables users and builders to look up transaction, message, account, and trace records for detailed visibility into the movement of assets. A "sent" status in your wallet does not guarantee that assets arrived at the intended recipient. Verifying actual receipt requires reviewing not just the transaction hash but also all related messages and trace records through trusted APIs or explorers.
Notably, neither public APIs nor explorers can confirm who controls the destination address. A completed on-chain record only means the transfer processed; it does not establish recipient control, off-chain ownership, or eligibility for a reward. Pending or partial transactions—sometimes shown as "in progress"—should not be treated as final, especially when interacting with campaigns, quests, or DApps relying on on-chain triggers.
For users and builders, the implication is clear: always check both transaction and message or trace details through official documentation and trusted interfaces. Before proceeding with any action that depends on on-chain proof—such as claiming rewards, providing access, or settling payments—verify every step of the process.
Risks in Relying on Public API Responses
Public APIs and explorers (such as those using TON Center API v3) support tracing via transaction, message, and trace endpoints, but these data sources have important limits for verifying asset transfers. API responses can show transaction and message details, including timestamps, amounts, and involved addresses, but they do not guarantee that the listed receiving address is owned or controlled by the intended party. No explorer or public API validates real-world identity or ownership behind addresses.
Incomplete or pending records are also problematic. For example, an API might show a transaction as "sent" or "pending" in the sender’s wallet, but that does not mean the destination account received the funds or that the transfer is final. Mistaking such records as proof of completed transfers exposes users and builders to risks, especially when backend errors or network delays result in only partial updates.
Both developers and users need to check if a message or transaction was included in a block, review the state of the destination account, and, for jettons, consult the relevant token master contract to confirm changes in final balances. Treat any explorer listing or API response that implies settlement as unconfirmed until validated by multiple sources using on-chain data.
TON Drop Hub take: Do not rely solely on API or explorer data as proof of settlement; always verify with direct contract and balance checks. This adds operational diligence but helps prevent premature assumptions and potential loss or misdirection of funds.
Tracing TON transactions through TON Center API v3 means looking at transaction and message records and then checking traces to see if a transfer completed on-chain. Wallets and explorers may show a "sent" status before funds are truly settled. For jettons and wrapped assets in particular, only the coordinated confirmation of transaction, message, and trace records indicates final delivery. Public APIs and explorers never validate ownership of the receiving address, and incomplete records cannot be safely treated as evidence of finalized transfers.
For builders and advanced users, depend on confirmed, settled trace data and directly verify the state of recipient accounts using official APIs. Consider wallet or explorer history as preliminary until message and trace review confirms actual asset arrival.
For more on navigating tools and DeFi on TON, see TON tools and DeFi.
Source reference: original source.