Traces

A trace is a set of messages and transactions produced by a single external message.

Each i-th transaction in the trace is triggered by a message sent during the action phase of some earlier j-th transaction, where j < i.

All messages and transactions in the trace are ordered by their logical time (lt), reflecting their logical dependencies. The diagram shows transactions on independent accounts, each triggered by an incoming message, with lt values indicated for every message.

Using traces in Tonviewer

In Tonviewer, traces are visualized as directed acyclic graphs (DAGs), where transactions are nodes and messages are edges, showing the full sequence of account state changes triggered by a single external message.

Tracing operations

Traces offer a high-level view of an operation, illustrating how multiple transactions and messages interact to produce the final result. Within the graph, related transactions are grouped into human-readable actions, providing developers with both the low-level transaction flow and the corresponding higher-level operations.

Example

The NFT transfer illustrates a single operation that consists of three transactions, each triggered by messages. To learn how to read traces, follow this article.

High-level access using API

To fetch transaction data, use the high-level GET /traces endpoint. This method allows you to retrieve all related transactions for a given operation, without parsing individual transactions.