Market context
System status · live

What is up, what is stale, what is broken.

Every data source, every API endpoint, every scanner — current state, last refresh, and the operating targets we track. Updates every minute on page load.

Loading…
Coverage report
Loading…
Coverage matrix

What is supported by chain and venue

validEthereumLaunch chain. Public-mempool MEV model + supported-token coverage are live.
unavailableBaseExpansion target. No calibrated public claim until realized-outcome error clears the gate.
unavailableArbitrumExpansion target. Sequencer-ordered L2 — public-mempool MEV assumptions do not transfer directly.
unavailableRobinhood ChainLive 1inch/0x quote comparison is available. Sequencer-ordered L2 with no public mempool → the public-mempool MEV model does not apply. No calibrated realized-outcome claim until the accuracy gate clears. Self-removing scam-token class disclosed as observed in the wild on this chain (Relay Protocol, 2026-07-09); token registry recognition does not rule it out, and no privilege-surface or can-sell evaluation is performed.
ChainVenueOrder flowState
EthereumUniswap V3public mempoolvalid
EthereumCurvepublic mempoolvalid
EthereumBalancerpublic mempoolpartial
EthereumCowSwapbatch auctionpartial
Ethereum1inch Fusionprivate / intentpartial
BaseUniswap V3sequencer-orderedunavailable
BaseBalancersequencer-orderedunavailable
BaseCowSwapbatch auctionunavailable
Base1inch Fusionprivate / intentunavailable
ArbitrumUniswap V3sequencer-orderedunavailable
ArbitrumCurvesequencer-orderedunavailable
ArbitrumBalancersequencer-orderedunavailable
ArbitrumCowSwapbatch auctionunavailable
Arbitrum1inch Fusionprivate / intentunavailable
Robinhood ChainUniswap V3sequencer-orderedunavailable

Base and Arbitrum are expansion targets. They are never reported as fully supported until realized-outcome calibration clears the gate — see the multichain expansion plan. Long-tail tokens are explicitly unsupported.

RPC health
Loading…
Power queue

Priority detector refresh requests

Power only
Supported scanner · MEV loss index

Power requests enter the detector-refresh queue with a response target and a 24-hour refresh target for supported public snapshots.

Operating targets

What we track

SurfaceTargetNotes
Snapshot freshness (most scanners)≤ 24 hoursDaily cron; stablecoins + HL + Across refresh hourly
MEV detector runhourly target100 blocks per run, finality depth 64
Power refresh requestsresponse target < 4h, refresh target < 24hSupported public detector snapshots; priority queue target, not a contractual freshness guarantee
API /api/snapshot/*< 500ms p95 targetEdge-cached 60s; falls back to filesystem in dev
Methodology disclosurepublic, hash-stamped/benchmark + /status both expose the version + hash
Public methodology change14 days notice targetPosted on /benchmark + Twitter before activation
Incident responseacknowledged < 4h, resolved < 24h targetFounder oncall; PagerDuty wired post-launch