Block Lottos vs Blockchair

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d90.4%98.9%
Uptime · 30d74.1%100%
P50 · ms657344
P95 · ms23742633
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no key (API docs state no key required)Free — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Block Lottos vs Blockchair: common questions

Which is more reliable, Block Lottos or Blockchair?

On our scheduled checks, Blockchair leads on measured uptime — Block Lottos at 90.4% versus Blockchair at 98.9% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Block Lottos or Blockchair?

Blockchair has the lower median latency in our checks — Block Lottos responds in 657 ms versus Blockchair at 344 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Block Lottos and Blockchair need an API key?

Neither needs a paid key — Block Lottos is callable with no signup, and Blockchair is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Block Lottos and Blockchair from the browser?

Yes — both Block Lottos and Blockchair send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Block Lottos and Blockchair free for commercial use?

Block Lottos has unclear commercial terms, and Blockchair has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.