quotedpartial / route warningsfailed / unsupportedcells show fee in bps; lower is better
Current provider status: coverage badges are live and derived from the current refresh. Li.Fi and Jumper can differ on large-size routing. Across now uses its official direct API: its current Solana-origin support is best interpreted as USDC out via swap + bridge, not a symmetric USDT -> USDT bridge. Mayan's public quote API is currently unstable, and Stargate now needs a LayerZero API key.
Show raw quote payloads
— click Refresh —
Volume + stablecoin share (Q1 + Q2)
Public Dune queries from dune_public_brand_queries.json. Unified Q1/Q2 rows expose volume_24h_usd, period volume, and aggregate stable columns where the query returns them. Legacy multi-row schemas still fill stable metrics from per-row symbols when present.
Bridge
24h volume (USD)
Volume (USD)
Stablecoin volume
Stablecoin %
Top stable token
Source
Stablecoin share: Estimated from each query’s row-level USD and symbol columns where present (same stable list as before). Bungee uses paginated tx sample — volume and stable metrics are biased. Across uses monthly aggregates. Query 6364512 mixes LiFi+Jumper integrators in SQL and outputs per chain_destination; “This Week's Volume” is a rolling window in the query (not calendar week). Final select has no token symbol — stable columns are usually —.
Transaction-size distribution (Q3 + Q4)
Public Dune snapshots per brand (dune_public_brand_queries.json). Same sources as dune_latest_results_probe.sh. Schemas differ — columns are best-effort; Li.Fi and Jumper share one query.
Bridge
Tx count 7d
Median tx size
% txns ≥ $100k
% txns ≥ $1M
Source
Dune batch = union of each brand’s primary_query_id and optional q34_query_id. Li.Fi uses split queries when configured (volume vs tx-size rows); Jumper stays its own row (5274443) until q34_query_id is set — Q3/Q4 stays No Latest Data there. Across/Stargate/Bungee/Mayan follow the same split pattern in JSON. Reads latest COMPLETED only.