Coin98 vs Dexari

Name: Coin98 vs Dexari OpenChainBench measurements
Creator: OpenChainBench
License: https://creativecommons.org/licenses/by/4.0/

Dexari leads on the only live benchmark. Dexari wins on Hyperliquid frontends builder revenue leaderboard ($548.18 vs $1.54).

Read methodology Last measured Thu, 27 Aug 2026 22:33:35 UTCWindow: rolling 24h1 shared benchmark

Coin98

Coin98 is a multi chain wallet super app whose perpetuals interface aggregates Hyperliquid alongside GMX and other venues, routing Hyperliquid fills via a registered builder code.

Dexari

Dexari is a pro trading UI for Hyperliquid perps focused on power users; orders carry a registered builder code for on-chain attribution.

Side by side measurements

Hyperliquid frontends builder revenue leaderboard

Trading

Provider	Builder fees collected	Volume routed	Users 24h	Effective fee bps	Time since last fill
Coin98provisional	$1.54	$3,845.99	1	0.040%	2.5 h
Dexari	$548.18	$663.4K	22	0.083%	2.7 min

Ranking is by raw builder fee revenue in USD, not by value for users. Bigger number means more fees collected via the on-chain builder code field. For the trader cost perspective, switch to the Effective fee bps companion tab. Native Hyperliquid UI orders carry no builder code and are excluded. Data from a local hl node tailing every fill on mainnet.

Frequently asked questions

Coin98 vs Dexari: which one is better?

Coin98 and Dexari are compared on 1 shared OpenChainBench benchmarks. Dexari leads on Hyperliquid frontends builder revenue leaderboard. See the live table on this page for every metric.

Which is cheaper, Coin98 or Dexari?

On the Hyperliquid frontends builder revenue leaderboard benchmark, Dexari leads at $548.18 versus Coin98 at $1.54 (provisional). Live measurement is updated continuously by the OpenChainBench harness.

How is the Coin98 vs Dexari comparison measured?

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.

How this pair was selected

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.