How visible liquidity walls are detected
The lab groups displayed orders into price buckets and compares each bucket’s quote notional with the median positive bucket in the selected band. A bucket above your chosen multiple is highlighted as a large cluster. Changing bucket size or the band changes the reference population and can change which levels qualify.
A highlighted wall is visible submitted liquidity. Public aggregated order books do not disclose whether it belongs to a whale, one institution or many smaller traders. The tool does not infer owner identity, hidden reserves or intent.
Pressure means book imbalance, not executed order flow
Within the selected distance from mid-price, the imbalance measure subtracts visible ask notional from visible bid notional and divides by their sum. Positive values mean more displayed bid notional in that band. Negative values mean more displayed ask notional.
This is a snapshot measurement of resting liquidity. It is not a count of buyer-initiated market trades, a liquidation estimate or a prediction of the next price move. Order cancellations and new submissions can change the ratio without a trade occurring.
Use persistence and depth together
The session history can show whether a large bucket appears repeatedly across retrieved snapshots. Repeated visibility is useful context, but polling misses changes between samples. Bucket matches are approximate and do not establish that exactly the same individual order remained in the queue.
Compare the wall with cumulative depth and your intended order size. A visually large cluster several percent away may matter less to immediate execution than thinner liquidity close to the spread. The chart includes only the returned levels, so an empty part of the view can mean missing coverage rather than no market liquidity.
Keep timing, candles and samples separate
The price chart uses completed hourly OHLC candles. Depth and imbalance use more recent order-book observations. They describe different time scales. The source timestamp is shown where available; receipt time is identified when the endpoint does not include an exchange timestamp.
Sample mode is explicitly labelled and uses synthetic data to explore the interface. Live requests require your action. Optional polling runs only while enabled and the page is visible. Neither mode submits orders or accesses private account data.
Questions about this tool
Are large Bitcoin buy and sell walls proof of whale positions?
No. A visible wall is a large cluster of submitted orders at nearby prices. Aggregated public data cannot identify the owner or establish their intent, and orders can be cancelled.
Does positive order-book pressure predict an upward price move?
No. It describes more displayed bid notional than ask notional within the selected band. It is not executed trade flow, and liquidity can move before a trade fills.
Sources and further reading
Bybit order-book snapshot fields ↗Binance Spot market data ↗Measure usable depth before interpreting a large quote
A displayed Bitcoin order book is useful for asking how much quoted liquidity sits near the current market. Compare both sides over the same distance in basis points, then examine whether the returned levels actually reach that distance. A large total from an incomplete range should not be compared with a fully covered range as though both described the same market depth.
The relevant quantity for an execution scenario is the sequence of prices and sizes an order would consume. A narrow spread can coexist with little depth behind the best quote. Conversely, a large visible cluster farther away may have no effect on a small order near the midpoint. Cancellation, hidden liquidity and price movement between requests can change either result before a trade occurs.
Use persistence to describe repeated observations of a price bucket, not the lifespan or identity of an order. The next sample may contain different orders at the same price. For a planned transaction, combine a snapshot-based slippage estimate with explicit fees and a quantity limit; compare the result later with actual fills rather than treating the snapshot as an executable quote.
The additional depth comparison uses several symmetric midpoint bands. Its execution scenario walks visible asks for a quote-currency buy budget and visible bids for the same gross sell proceeds; those scenarios can trade different base quantities. Displayed costs exclude fees, cancellations and later liquidity. A coverage limit or partial fill must remain part of the interpretation rather than being treated as a completed order.
Read the source and freshness labels before using a result. Public feeds can be delayed, blocked or unavailable by market, region or browser. Pause stops this page's feed collection. No chart observation guarantees a fill, identifies an order's owner or establishes future returns.