POST /analyze call returns a fully structured TxReport with labeled intent, actor attribution, token flows, and supporting motif evidence, so your UI can focus on display logic rather than on-chain trace decoding.
What to Display
Intent Label
The plain-English description of what the transaction did — e.g., “Atomic arbitrage” or “Swap via aggregator”. Sourced from
classification.intent_label.Actor & Signer
The economic actor (who benefited) and the signing wallet (who paid gas). These are often different for smart wallets, aggregators, and MEV bots.
Token Flows
A visual send/receive summary: which tokens went in, which came out, and the USD value of each movement — sourced from
economics and inventory_deltas.Gas & Net USD
Gas cost in USD alongside the net economic result before and after gas, so readers can see the true cost of the transaction.
Motifs (Proof)
The structural primitives that the engine matched — swap hops, closed value flows, flash loan receipts — listed as supporting evidence for the intent label.
Explorer Link
A direct Etherscan link for one-click cross-referencing on the public block explorer, sourced from
tx.etherscan_url.Fields to Use
The table below maps each visualizer component to the exactTxReport field that supplies it.
Actor vs. Signer
In a simple token transfer the signer and the economic actor are the same wallet. In more complex transactions they diverge:- Aggregators — a user signs a transaction to a DEX aggregator router; the router is the on-chain actor but the user is the economic beneficiary.
- Smart wallets — a relayer EOA signs a meta-transaction on behalf of an ERC-4337 account or a Gnosis Safe.
- MEV bots — a bot EOA signs the transaction, but the bot contract (or the searcher behind it) is the real economic actor.
classification.actor_matches_signer is false, display both addresses separately and add a visual indicator (e.g., a tooltip or badge) explaining the discrepancy. This distinction matters for compliance, attribution, and UX clarity.
Token Flow Diagram
Groupinventory_deltas by subject and then by direction to build a per-address inflow/outflow table. This gives you the raw material for a Sankey diagram, a flow table, or a simple ”+/−” token list.
Reverted Transactions
Whenclassification.intent_kind is "TransactionReverted", the transaction failed on-chain. No token transfers occurred, but the signer still paid gas. In this case:
- Skip the token flow section entirely — there is nothing to show.
- Display a failure card with the revert reason (if available) and the gas cost.
- Use
economics.fee_usd.textto show how much the failed transaction cost.
Example: Rendering Intent Label and Actor
The snippet below shows a minimal React component that renders the headline information from aTxReport.