Perp DEX volume share, live 24h notional ranked
TradingHyperliquid
Leads$3.68B
- p99
- $5.73B
- rank
- #1
- samples
- 2,880
Jupiter Perps
Trails$103.42M
- p99
- $141.02M
- rank
- #13
- samples
- 2,880
Split decision: Hyperliquid leads on Perp DEX volume share, live 24h notional ranked ($3.68B vs $103.42M) and Most tradable markets on a perp DEX, live count per venue (178 vs 3); Jupiter Perps leads on Perp DEX token P/E ratio 2026 (30.6x vs 102.4x) and Perp DEX price to fees (5.14x vs 19.4x). Data as of 2026-10-05 UTC.
Onchain perp DEX on the Hyperliquid L1. Fully onchain orderbook with sub-second matching, no off-chain matching engine.
Solana swap aggregator. REST APIs for quotes, swap routing, price, and token lists across Solana DEXs.
Hyperliquid
Leads$3.68B
Jupiter Perps
Trails$103.42M
Hyperliquid
Leads178
Jupiter Perps
Trails3
Hyperliquid
Trails102.4x
Jupiter Perps
Leads30.6x
P/E = fully diluted valuation (CoinGecko) divided by annualized protocol revenue (DeFiLlama dailyRevenue, 30-day trailing average x365). Protocol revenue = fees accruing to the treasury or token holders, not total user fees. Tokens without a CoinGecko listing show no P/E. FDV reflects total supply at current price, not circulating supply; tokens with large unvested allocations will show inflated FDV-based P/E. Updated hourly.
| Provider | P/F ratio | FDV / fees | P/S | Fees 30d | Revenue 30d | Float | Open interest | Fees / OI |
|---|---|---|---|---|---|---|---|---|
| Hyperliquid | 19.4x | 83.4x | 23.8x | $87.53M | $71.31M | 23.3% | $8.56B | 0.124x |
| Jupiter Perps | 5.14x | 10.6x | 14.8x | $18.05M | $6.27M | 48.4% | $47.30M | 4.64x |
P/F = circulating market cap (CoinGecko) / annualized fees (DeFiLlama dailyFees, trailing 30d x 365/30), on the DeFiLlama parent the token accrues from. Fees include the share paid to liquidity providers; P/S uses protocol revenue only. Low-float tokens show a much higher FDV/F than P/F. Pre-TGE venues are listed unranked with fees and OI, no ratio. A low multiple is not a recommendation.
Hyperliquid
Leads0.278x
Jupiter Perps
Trails1.033x
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.
| Provider | P/F ratio | vs category | Fees MoM | Token 30d | Float | FDV / fees | Market cap | Fees 30d | Revenue 30d | P/S | TVL | Supply 30d | Supply 90d |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hyperliquid | 19.4x | 2.17x | 3.43% | 8.88% | 23.3% | 83.5x | $20.70B | $87.53M | $71.31M | 23.9x | $7.53B | - | - |
| Jupiter Perps | 5.13x | 0.574x | - | 51.8% | 48.4% | 10.6x | $1.13B | $18.05M | $6.27M | 14.8x | $2.85B | 0.012% | 0.012% |
A screen, not a verdict, and not advice. P/F = circulating market cap (CoinGecko) / annualized fees (DeFiLlama, trailing 30d x 365/30) summed across every fee adapter that accrues to the token. Fees include the share paid to liquidity providers. A low multiple can mean the market expects fees to fall, that the fees were incentivised, or that the token has no claim on them. Read it with the float, the category median and the monthly fee trend, then do your own work.
Hyperliquid and Jupiter Perps are compared on 6 shared OpenChainBench benchmarks. Hyperliquid leads on Perp DEX volume share, live 24h notional ranked. Jupiter Perps leads on Perp DEX token P/E ratio 2026. See the live table on this page for every metric.
On the Perp DEX volume share, live 24h notional ranked benchmark, Hyperliquid leads at $3.68B versus Jupiter Perps at $103.42M. Live measurement is updated continuously by the OpenChainBench harness.
On the Perp DEX token P/E ratio 2026 benchmark, Jupiter Perps leads at 30.6x versus Hyperliquid at 102.4x. 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.