Skip to main content
Sigvex

Transaction Trace

Trace one transaction end to end — token transfers, DEX swaps, and cross-chain bridge legs with automatic destination pairing.

Transaction Trace takes a single transaction hash and reconstructs what actually happened to value inside it: the token transfers, the DEX swap hops, and — the part that usually breaks a manual trace — the bridge crossings that carry funds off to another chain.

Why it exists

Following money through one transaction sounds simple until it hits a bridge. A raw receipt shows a deposit event and then the trail goes cold, because the destination leg lives in a different transaction on a different chain. Transaction Trace pairs the two sides for you where it can, and hands you a deterministic correlation key to search for when it can’t.

Who uses it

  • Forensics analyst — follows stolen or laundered funds across swaps and bridges from a single starting hash.
  • Auditor — inspects exactly what a suspicious transaction moved and where the value ended up.

How to open it

  1. Sidebar → Monitoring → Transaction Trace.
  2. Direct URL — /tx-trace (deep-linkable as /tx-trace?network=…&tx=…, which runs the trace on load).

Running a trace

  1. Paste a 32-byte transaction hash (0x…).
  2. Pick the network the transaction is on. This control follows the global network picker, so the two stay in agreement.
  3. Click Trace.

Reading the results

The report groups value movement into sections:

  • Bridge crossings — value leaving this chain, paired with its destination arrival where one is found.
  • Bridge arrivals — when the transaction is itself the destination side of a cross-chain transfer, keyed back to the source deposit.
  • DEX swaps — AMM hops, with the tokens and amounts swapped.
  • Token transfers — the direct transfer legs.

When a bridge destination isn’t carried in-band, the report shows the correlation key — a deterministic value you can search for on the destination chain to continue the trace there.

Limits

  • Tracing covers EVM networks.
  • Cross-chain pairing depends on the bridge carrying enough information; when it doesn’t, the correlation key is the lead to follow manually.
  • Entity Labels — attribution surfaces on the addresses in a trace.
  • Watchlist — set a subject to alert on future movement.