What actually happens under a STONfi transaction?
On TON, a single user action can trigger multiple underlying messages. What looks like a simple swap on the surface often involves several steps across different contracts. STONfi’s Transaction Action Tree is designed to make sense of that complexity.
Instead of treating every raw message as an isolated event, it groups recognized activity into higher-level actions such as:
• Swaps
• Liquidity operations
• Fee collection
• Refunds
• Token burns
This is not a native TON data structure. The blockchain still stores the original messages. STONfi adds a protocol-aware layer that interprets those messages and organizes them into clearer operations. The current API returns a flattened list rather than a nested visual tree, but the interpretation still helps map complex flows into something more readable.
For users and builders trying to understand what really happened during a transaction, this structure is useful. It turns a series of technical messages into a more practical sequence of actions.
Curious how others track on-chain activity on TON do you usually dig into the raw messages or rely on higher-level interpretations?
$GRAM
On TON, a single user action can trigger multiple underlying messages. What looks like a simple swap on the surface often involves several steps across different contracts. STONfi’s Transaction Action Tree is designed to make sense of that complexity.
Instead of treating every raw message as an isolated event, it groups recognized activity into higher-level actions such as:
• Swaps
• Liquidity operations
• Fee collection
• Refunds
• Token burns
This is not a native TON data structure. The blockchain still stores the original messages. STONfi adds a protocol-aware layer that interprets those messages and organizes them into clearer operations. The current API returns a flattened list rather than a nested visual tree, but the interpretation still helps map complex flows into something more readable.
For users and builders trying to understand what really happened during a transaction, this structure is useful. It turns a series of technical messages into a more practical sequence of actions.
Curious how others track on-chain activity on TON do you usually dig into the raw messages or rely on higher-level interpretations?
$GRAM
