Perp DEX volume share, live 24h notional ranked
TradingGMX
Trails$127.30M
- p99
- $136.37M
- rank
- #17
- samples
- 2,880
Jupiter Perps
Leads$715.83M
- p99
- $800.41M
- rank
- #9
- samples
- 2,880
GMX leads on 3 of 4 shared benchmarks, Jupiter Perps on 1. GMX wins on Perp DEX token P/E ratio 2026 (1.526x vs 38.8x), Perp DEX price to fees (1.282x vs 4.77x), Price to fees across DeFi (1.255x vs 4.58x). Jupiter Perps wins on Perp DEX volume share, live 24h notional ranked ($715.83M vs $127.30M). Data as of 2026-10-30 UTC.
Perp DEX on Arbitrum and Avalanche. Pool-based execution against GLP and GM vaults, oracle-priced trades with no orderbook.
Solana swap aggregator. REST APIs for quotes, swap routing, price, and token lists across Solana DEXs.
GMX
Trails$127.30M
Jupiter Perps
Leads$715.83M
GMX
Leads1.526x
Jupiter Perps
Trails38.8x
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 |
|---|---|---|---|---|---|---|
| GMX | 1.282x | 1.292x | 1.534x | $5.39M | $4.54M | 100.0% |
| Jupiter Perps | 4.77x | 9.91x | 18.8x | $14.79M | $3.76M | 48.4% |
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.
GMX
No data in window
Jupiter Perps
Trails7.87x
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 | Token 30d | Float | FDV / fees | Market cap | Fees 30d | Revenue 30d | P/S | TVL | Supply 30d | Supply 90d |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| GMX | 1.255x | 0.160x | - | 100.0% | 1.255x | $84.54M | $5.54M | $4.73M | 1.468x | $230.60M | 2.22% | 2.31% |
| Jupiter Perps | 4.58x | 0.584x | - | 48.4% | 9.47x | $859.74M | $15.43M | $3.94M | 17.9x | $2.18B | - | - |
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.
GMX and Jupiter Perps are compared on 5 shared OpenChainBench benchmarks. GMX leads on Perp DEX token P/E ratio 2026. Jupiter Perps leads on Perp DEX volume share, live 24h notional ranked. See the live table on this page for every metric.
On the Perp DEX token P/E ratio 2026 benchmark, GMX leads at 1.526x versus Jupiter Perps at 38.8x. Live measurement is updated continuously by the OpenChainBench harness.
On the Perp DEX volume share, live 24h notional ranked benchmark, Jupiter Perps leads at $715.83M versus GMX at $127.30M. 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.