How to Read a Full-Depth Crypto Order Book
Move from best bid and ask to individual levels, cumulative depth, walls, thin regions and a worked slippage estimate—then learn what even a deep live book cannot prove.
A full-depth crypto order book is a price-by-price view of the resting buy and sell quantities currently known for one pair on one venue. “Full depth” does not mean every possible order in the world. It means looking beyond a short top-of-book list and retaining as many received price levels as the source and the local accumulator can provide.
The visual below is deliberately simplified. Price runs vertically. Width represents quantity: first at individual levels, then as a running total away from the market. You can compare it with the live BTC/USDT Order Hull while reading.
1. Start at the spread, not at the largest wall
The best bid is the highest displayed buy price. The best ask is the lowest displayed sell price. Their difference is the spread. The simple midpoint is halfway between them: (best bid + best ask) / 2. It is a reference value, not necessarily a price at which anyone is offering to trade.
Read outward from that center. Ask prices rise as you move away above the market; bid prices fall below it. A row is one price level, not one person or one order: exchanges commonly aggregate all visible quantity at the same price.
2. Separate individual levels from cumulative depth
In individual levels mode, a width answers: “How much visible quantity rests at this exact price?” A long bar at one price can stand out even when neighboring prices are thin.
In cumulative depth mode, each point includes that level plus every nearer level on the same side. For asks, cumulative depth at price p is the displayed sell quantity from the best ask through p. For bids, it is the displayed buy quantity from the best bid down through p. The cryptonabs Order Hull is this shape drawn on the chart's price axis.
A cumulative curve should normally widen away from the spread because quantities are being added. That visual fact does not mean demand or supply is growing through time; it is a spatial sum across prices at one current state.
3. Read walls, shelves and thin regions cautiously
A wall or shelf is a concentration of displayed quantity around one price or a small price range. It produces a sudden widening at individual level or a steep step in cumulative depth. A thin region is the opposite: little displayed quantity spans a comparatively large price interval.
These are descriptions, not predictions. A large order can be cancelled, moved, partly hidden or executed. Repeatedly placing and cancelling orders may also create a misleading impression of interest; this behavior is often called spoofing. A wall therefore is not confirmed support or resistance, and a thin region does not guarantee that price will cross it.
4. Estimate slippage level by level
Slippage is the difference between a reference price—often the best quote when the estimate begins—and the volume-weighted average price across the levels needed for an order. Consider a simplified ask book and a hypothetical market buy for 1.50 BTC:
| Ask price | Available BTC | Bought BTC | Cost in USDT |
|---|---|---|---|
| 100.00 | 0.50 | 0.50 | 50.00 |
| 100.50 | 0.50 | 0.50 | 50.25 |
| 101.00 | 1.00 | 0.50 | 50.50 |
The estimated total is 150.75 USDT for 1.50 BTC, so the volume-weighted average is 100.50 USDT. Relative to the initial best ask of 100.00, the estimate is 0.50 USDT, or 0.5%, higher. Fees are excluded. The real result can differ because the book can change before and during execution, and this viewer does not execute trades.
5. Understand snapshot, updates and accumulated far levels
A live local book starts from a snapshot and then applies sequenced absolute updates. “Absolute” means an update replaces the stored quantity at its price level; a zero quantity removes that level. Sequence identifiers allow a missed interval to be detected and the book to be rebuilt.
The cryptonabs acquisition process continues maintaining its supported book without a browser connected. A visitor receives the server's already accumulated current state and then live updates. Opening a page is not what starts exchange collection, and the guide itself creates no additional market-data request.
The source has a finite initial snapshot. Its public depth endpoint currently documents at most 5,000 entries per side. A farther level outside that initial range can become known later if the diff stream updates it, so a long-running local accumulator may retain more distant known levels than a fresh snapshot alone. The exact update and snapshot fields are described in the official Spot WebSocket market-stream documentation and the official Spot market-data REST documentation.
There is an important limit: if the service was offline when a distant order was removed, that cancellation may not be learned immediately after restart because the level can still be outside the next finite snapshot. A later update at that price replaces the remembered quantity and corrects it. The accumulated hull is useful orientation, not a mathematically complete audit of every resting order.
6. Know what full depth still leaves out
- Hidden liquidity: iceberg or otherwise undisclosed size is not visible in the public book.
- Cancellations: displayed orders can disappear before they are reached.
- One venue: one exchange and pair are not the global crypto market.
- Finite source coverage: the initial snapshot has a documented level limit, while distant accumulated levels depend on received updates.
- No queue certainty: aggregated level size does not show your hypothetical place in an execution queue.
- No forecast: depth describes displayed liquidity; it does not predict direction.
For the shorter introduction, read How to Read a Bitcoin Order Book and Market Depth Chart. For failure modes and stale-data checks, continue with the limits of public live order-book data. This article is informational technical context, not financial advice or a buy, sell or hold recommendation.