live MEV & contention on Monad ← parascan API connecting…
Sandwich attacks, atomic arbs and orderbook contention, decoded live from mainnet. Part of parascan · chain 143.

Watch your pool — is a specific pool or token getting sandwiched?

Hourly activity — last 48h, UTC, each panel on its own scale

Where the flow trades — decoded swaps by venue

Top extractors

Attacker (tx origin)SandwichesExtractedKuruAMMLast block
waiting for first detections…

Most contended pools — by decoded swaps

PoolVenueSwapsSandwiched
waiting…

Sandwich attacks — newest first, live + backfilled history

VenueBlocksAttackerVictimVictimsExtractedViaFront / back tx
No sandwiches detected yet.

Atomic arb candidates — one tx, multiple pools

WhenBlockPools touchedTx
waiting…

Method — how these numbers are made

Sandwiches

A front-run and a back-run bracketing a victim on one pool, within 3 blocks. On AMMs (Uniswap v2/v3/v4 deployments) the bracket is confirmed by transaction sender or a shared bot contract, resolved with batched, retried RPC lookups. On the Kuru CLOB, one market order emits one Trade per maker fill, so fills are first collapsed into taker actions (tx × book × direction), then bracketed by the txOrigin the event itself carries — no per-tx lookups at all.

Extracted value (USD)

“Extracted” is gross value captured, not a bot's wallet profit. Per sandwich, the attacker's front+back token deltas are netted on the sandwiched pool itself (what the pool paid out minus what was paid in, per token — wallet flows can't be used because Monad bots settle in native MON and park inventory in vault contracts). Leftover inventory is marked at the victim's own execution price. Stables are $1; MON is priced from live WMON/USDC v3 swaps. It is measured before gas (attacker gas is shown separately). A negative figure means the bracket lost money — bots misfire, and sandwich each other. The per-attacker column is the sum of that bot's own brackets; the site total sums every bracket across all bots, so the many losing bots pull it far below what the top extractors each make.

Atomic arb candidates

One transaction swapping on two or more distinct pools in the same block. These are candidates, not confirmed profit — token flows are not yet netted.

Coverage

Every Swap/Trade event on Monad mainnet from the public RPC: Uniswap v2, v3, v4 (and forks emitting the canonical topics — PancakeSwap v2 pools land in the v2 bucket), PancakeSwap v3, LFJ Liquidity Book, plus Kuru orderbooks. Aggregators (Kyberswap, Matcha…) route into these pools, so their flow is covered by construction. Live blocks stream in continuously; history is backfilled with the exact same detectors. All detection is heuristic — figures are candidates for verification, not settled ground truth.