Crypto market analytics: quotes, depth and venue status in one pass
Analytics usually means a wall of charts assembled from sources that were read at different times. This page does the opposite: quotes, reported depth and each venue's own service status from a single observation pass, with the time printed above them, so the three can actually be compared with each other.
BTC bid and ask by exchange
BTC top-of-book quotes by exchange, with depth and venue status from the same pass.
Observed · Stale
| Exchange | Quote currency | Best bid | Best ask | Spread |
|---|---|---|---|---|
| Coinbase | USD | 83,334.40 | 83,334.41 | 0.0012 bps |
| Kraken | USD | 83,341.60 | 83,341.70 | 0.012 bps |
| OKX | USDT | 83,390.50 | 83,390.60 | 0.012 bps |
| Binance | USDT | 83,392.47 | 83,392.48 | 0.0012 bps |
| Bybit | USDT | 83,384.50 | 83,384.60 | 0.012 bps |
Swipe horizontally for more columns.
What you can do with it
Start from the overview, then go narrow
The workspace exists to choose what to open: a pair, a market, a trader or an event. The detail views each carry their own coverage and source time, and the useful discipline is to check that before comparing two of them.
Compare like with like
A quote, a historical performance snapshot and a recent activity feed describe different things over different windows. Reading them as one picture is where most analytical mistakes on this kind of page come from.
Use venue status as a filter
Before concluding anything from a venue's numbers, check whether the venue said it was healthy. The status column is on the same page for that reason.
Move between crypto and prediction markets
The same workspace links the prediction desk, trader research and event monitors. Rate expectations and crypto liquidity move together often enough that keeping them in separate products loses the connection.
How it works
One pass, several sources
The tables here are drawn from the same refresh cycle, which is what makes the comparison meaningful. Each still carries its own observation time, because a cycle can succeed on one source and fail on another, and the page shows which rather than averaging over the difference.
Availability of a page is not freshness of its data
A workspace that loads is not a workspace whose every feed is current. Vultax's rule throughout is that a section states its own status and marks itself stale rather than presenting a retained value as a new one, and a failed refresh shows retained, dated observations rather than a blank page.
Missing is not zero
Where a venue did not report, the cell says unavailable. Rendering a dash or a nought there would turn 'we did not observe this' into 'this was nothing', which is a much stronger claim and, often enough, a wrong one.
The three questions a workspace should answer quickly
Where should I look? That is what an overview is for, and the honest version of it is a set of pointers with their own coverage rather than a single composite number that hides which input moved.
Is what I am looking at current? Every view on this site answers that on its own, because a workspace that answers it once at page level will eventually be wrong about one of its panels and will not know.
What would change my mind? The most useful thing a research surface can do is make disagreement visible — two venues quoting differently, depth that contradicts turnover, flow that contradicts price. Those are on separate rows on purpose, and a dashboard that averages them away has removed the only interesting content.
What each plan gives you here
What a plan changes on this surface.
| What you get | Free | Essential | Premium | Pro |
|---|---|---|---|---|
| Prediction market prices, charts and market pages | Included | Included | Included | Included |
| Crypto prices, order books and depth | Included | Included | Included | Included |
| Six-domain Vi IQ detail on every pair | Not included | Included | Included | Included |
| Historical lookback | Current views | 3 days | 7 days | 30 days |
Compared with the big market-data dashboards
The large dashboards cover far more assets and far more chart types than Vultax does. What they generally do not do is state, per table, when the figure was observed, which sources failed, and what the coverage was. On a page whose whole purpose is comparison, those three lines are the difference between analysis and decoration.
Competitor details last checked . They describe other products as their operators published them, not as an assessment of them.
Every table on this page
Each table carries its own source, observation time, coverage and limits, and can be taken away as JSON or CSV. A missing value means the source did not report it; it is never rendered as a zero.
01 Market snapshot
Reported BTC market depth
Reported cost to move the market by 2%, alongside the corresponding BTC pair and reported turnover.
StaleObserved 5 rowsThe source observation is older than this table’s 60-minute freshness window.
| Exchange | Pair | +2% depth (USD) | −2% depth (USD) | Reported 24h volume (USD) | Pair status |
|---|---|---|---|---|---|
| Binance | BTC/USDT | 23,046,992 | 29,212,519 | 1,717,119,589 | No flag reported |
| Coinbase | BTC/USD | 20,071,768 | 32,287,793 | 643,874,512 | No flag reported |
| Kraken | XBT/USD | 23,442,417 | 19,330,123 | 271,550,457 | No flag reported |
| OKX | BTC/USDT | 12,199,696 | 21,009,139 | 520,838,975 | No flag reported |
| Gate | BTC/USDT | 19,878,716 | 30,984,118 | 877,743,777 | No flag reported |
Scroll to see all columns.
CoverageCoinGecko tickers for the configured exchanges; the pack selects each venue’s highest-volume BTC USD, USDT or USDC pair.
Depth and turnover are reported by the upstream source, not independently verified executable liquidity.
The upstream pack rounds amounts and may convert missing depth or volume to zero; a reported zero is not proof of no liquidity.
02 Market snapshot
Exchange service status
The service-status responses already collected by Vultax.
StaleObserved 5 rowsThe source observation is older than this table’s 20-minute freshness window.
| Exchange | Indicator | Source message |
|---|---|---|
| Coinbase | none | All Systems Operational |
| Kraken | minor | Partially Degraded Service |
| Binance | none | normal |
| OKX | none | All systems operational |
| Kalshi | none | exchange active |
CoverageConfigured exchange status endpoints; operational status does not establish feed completeness or execution access.
The upstream status messages retain the provider’s meaning; different providers use different status vocabularies.
Questions
What does the analytics workspace cover?
Crypto price and liquidity context, prediction market research, trader analytics and market activity, as separate views with their own coverage.
How fresh are the figures?
Each table states its observation time and marks itself stale against its own window. The freshness of a page is never asserted at page level.
Do I need an account?
Not for this page. The app's workspaces open with a free account; the deeper crypto panels sit on Essential and above.
Why do two views disagree?
Usually because they measure different populations over different windows. Each view names its own, which is what makes the disagreement readable instead of alarming.
Can I get the data programmatically?
Every table exports as JSON and CSV from this site, free and without an account.
Is there a single dashboard number?
No, and that is deliberate. A composite of sources with different freshness and different populations is a number nobody can check, and it goes wrong quietly.
Coverage and methodology
- Public tables mirror existing Vultax source packs. They do not include account data, private watchlists or the complete app dataset.
- Source time, coverage and limitations apply to each table. Missing values are unavailable, not zero.
Published research behind this page
Dated write-ups of the same sources. A figure in a study describes the window it was written about, not the snapshot above.
Published estimates put fake or non-economic bitcoin volume at 51% to 95%, and above 70% on unregulated venues. Why the studies disagree, why depth and slippage judge a venue better than volume (Binance: 64.3% of volume, 30.7% of depth, per Kaiko), and what to check yourself.
Order-book feed latency on 16 crypto exchanges: medians from 35.0 ms (Coinbase) to 111.5 ms (BTSE), a 95th percentile of 288–590 ms on every venue, and data in every minute of the day. Plus the coverage check that catches a feed that stays connected and stores almost nothing.
Keep reading
Take this into the workspace
These tables are public. A free account opens the workspace behind them.
A free account needs no payment card and starts no subscription. Figures on this page were observed . JSON · Markdown · Schema