Perp DEX volume share, live 24h notional ranked
TradingJupiter Perps
Trails$290.60M
- p99
- $353.45M
- rank
- #12
- samples
- 2,876
Kalshi
Leads$1.45B
- p99
- $1.56B
- rank
- #5
- samples
- 2,876
Jupiter Perps leads on 1 of 3 shared benchmarks, Kalshi on 2. Jupiter Perps wins on Perp DEX volume to open interest (3.21x vs 40.5x). Kalshi wins on Perp DEX volume share, live 24h notional ranked ($1.45B vs $290.60M), Most tradable markets on a perp DEX, live count per venue (21 vs 3). Data as of 2026-09-23 UTC.
Solana swap aggregator. REST APIs for quotes, swap routing, price, and token lists across Solana DEXs.
CFTC-regulated US prediction market exchange. REST trade API (trade-api/v2) with documented per-tier rate limits; the market data WebSocket requires authentication.
Jupiter Perps
Trails$290.60M
Kalshi
Leads$1.45B
Jupiter Perps
Trails3
Kalshi
Leads21
Jupiter Perps
Leads3.21x
Kalshi
Trails40.5x
The ratio is a screen, not a verdict. Both terms are the venue's own figures (24h volume and open interest as each API reports them, in USD), so a venue that counts both legs of a fill moves its ratio without changing anything real. A very low ratio (Ostium, 0.2x) means positions held for days on thin daily volume; a very high one (Kalshi, above 40x) means a day of trading dwarfs what stays open. The bands in the methodology say what each range usually means.
Jupiter Perps and Kalshi are compared on 3 shared OpenChainBench benchmarks. Jupiter Perps leads on Perp DEX volume to open interest. Kalshi leads on Perp DEX volume share, live 24h notional ranked. See the live table on this page for every metric.
On the Perp DEX volume to open interest benchmark, Jupiter Perps leads at 3.21x versus Kalshi at 40.5x. Live measurement is updated continuously by the OpenChainBench harness.
On the Perp DEX volume share, live 24h notional ranked benchmark, Kalshi leads at $1.45B versus Jupiter Perps at $290.60M. Live measurement is updated continuously by the OpenChainBench harness.
Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.
Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing; panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.