BlockVectra vs PublicNode

PublicNode leads on both live benchmarks. PublicNode wins on Unichain RPC endpoints (52 ms vs 138 ms), Fraxtal RPC endpoints (68 ms vs 136 ms). Data as of 2026-11-03 UTC.

Read methodology Last measured Window: rolling 24h2 shared benchmarks
BlockVectra logo
BlockVectra

RPC gateway with keyless public endpoints (3 requests per second per IP, 1,000-block history window). Measured on the Ink, Unichain and Fraxtal RPC pages.

PublicNode logo
PublicNode

Public no-key RPC service operated by Allnodes covering 70+ chains. JSON-RPC and WebSocket endpoints with archive support on most networks.

Side by side measurements

Unichain RPC endpoints: free public URLs by latency

RPCs

BlockVectra

Trails

138 ms

p99
781 ms
rank
#4
samples
832

PublicNode

Leads

52 ms

p99
303 ms
rank
#1
samples
4,318

Per region

RegionBlockVectraPublicNode
US-East121 ms25 ms
EU-West50 ms34 ms
Singapore241 ms98 ms
RPC latency
BlockVectran/aPublicNoden/a

Fraxtal RPC endpoints: free public URLs by latency

RPCs

BlockVectra

Trails

136 ms

p99
754 ms
rank
#4
samples
834

PublicNode

Leads

68 ms

p99
337 ms
rank
#2
samples
4,320

Per region

RegionBlockVectraPublicNode
US-East122 ms50 ms
EU-West49 ms34 ms
Singapore239 ms120 ms
RPC latency
BlockVectran/aPublicNoden/a

Frequently asked questions

BlockVectra vs PublicNode: which one is better?

BlockVectra and PublicNode are compared on 2 shared OpenChainBench benchmarks. PublicNode leads on Unichain RPC endpoints. See the live table on this page for every metric.

Which is faster, BlockVectra or PublicNode?

On the Unichain RPC endpoints benchmark, PublicNode leads at 52 ms versus BlockVectra at 138 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the BlockVectra vs PublicNode 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.