uDEX MONITOR
PulseChain connecting

Execution intelligence

Every swap has a story.

See the route, the venues, the tokens, and whether value was split or simply carried forward—without reading a raw transaction trace.

Router watch
Selected execution DAI → WPLS
Route structure V2 × 10 · V3 × 1 11 venues crossed
Value flow 100% sequential No split detected
Execution state Successful Trace-ready route

The execution story

From intent to outcome

Trace-ready

V2 venue V3 venue value carried forward

Readable trace

The route, in chapters

i

This monitor reads public chain data. A route is built from executed V2/V3 swap calls and pool events; unresolved token labels remain as addresses rather than guesses.

Monitor settings

Keep the watch current

uDEX can change routers. Update the watched address here; it is kept in this browser and used by the next sync.

When this page is in the background, it checks every 5 minutes and catches up from the last checked block when you return.

Telegram room

Keep conversation nearby

Add the public room link for one-click context. Private rooms and message alerts need a small server-side bot bridge—never place a Telegram bot token in this website.