Other vs Quasar

Quasar leads on the only live benchmark. Quasar wins on Ethereum block builder market share (16.4% vs 9.03%).

Read methodology Last measured Window: rolling 24h1 shared benchmark
Other logo
Other

Aggregate long-tail bucket, not a single provider. On the block-builder bench it collects blocks whose extraData tag is not in the curated attribution table; every raw string is logged so named rows can be added as the table grows.

Quasar logo
Quasar

Ethereum block builder self-described as neutral and non-censoring, second-largest by extraData share. The operating entity is not publicly named; identity rests on the `quasar` extraData self-label and the quasarbuilder.eth fee recipient.

Side by side measurements

Ethereum block builder market share

Trading

Other

Trails

9.03 %

p99
9.03%
rank
#4
samples
648

Quasar

Leads

16.4 %

p99
16.4%
rank
#3
samples
1,177

Attribution relies on the extraData tag each builder voluntarily stamps. A builder can change or strip its tag; unrecognized tags land in Other and raw strings are logged so the table grows. The Vanilla row (locally built) could be marginally overstated if a builder uses a client-default tag; the relay cross-check surfaces this. High share is a centralization datapoint, not a quality ranking.

Rolling 24h · Block share (24h)Raw JSON

Frequently asked questions

Other vs Quasar: which one is better?

Other and Quasar are compared on 1 shared OpenChainBench benchmarks. Quasar leads on Ethereum block builder market share. See the live table on this page for every metric.

Which is more reliable, Other or Quasar?

On the Ethereum block builder market share benchmark, Quasar leads at 16.4% versus Other at 9.03%. Live measurement is updated continuously by the OpenChainBench harness.

How is the Other vs Quasar 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.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.