Crypto depth history: the recorded Bybit order book, day by day
The Crypto history tab of the heatmap route reconstructs a completed UTC day of the Bybit order book (Spot or USD-M Perp) from daily archives or from locally copied collector minutes, and draws it as a static depth image with measured coverage and gaps.
Senzoukria · Documentation · Updated September 2026
Where to find it
- Where
- Heatmap route → tabs Live / Crypto history → Historical order book
- Source
- Bybit · 200 levels per side · 1-second samples · peak resting liquidity in base units
- Defaults
- Market Bybit Spot, symbol BTCUSDT, Last UTC day = yesterday, Window 24 h
- Range
- Completed UTC days only, within the last 9 days
What it does
The heatmap route has two tabs. Live is the streaming heatmap. Crypto history is a separate screen, Historical order book, that never touches the live book: it asks the backend to download and reconstruct the depth of a finished UTC day, then paints a depth image on a canvas. Bids are drawn in teal, asks in orange, on a logarithmic intensity scale; blank columns have no observations.
Load history imports the requested days newest first, one archive at a time, and redraws after each day. Stop after this day interrupts a multi-day load once the current archive is done. A day that is not published is skipped with the message Some requested days are not published; available days remain visible.
After a load, the coverage line reports the provenance and the holes as measured by the backend: number of daily archives, number of collector minutes, observed seconds out of requested seconds, gap count and largest gap, and the first and last timestamps in UTC. A gap remains a gap; nothing is interpolated.
Settings
| Control | Default | What it changes |
|---|---|---|
| Market | Bybit Spot | Bybit Spot or Bybit USD-M Perp |
| Symbol | BTCUSDT | BTCUSDT, ETHUSDT or SOLUSDT |
| Last UTC day | Yesterday | Last day of the range; maximum yesterday, minimum today minus (10 − window days) |
| Window | 24 h | 24 h, 72 h or 168 h ending at the end of the selected day |
| Load history | — | Downloads and reconstructs the book, newest day first |
| Stop after this day | — | Shown while loading; ends the run after the current archive |
| Collector minutes folder (local validation) | empty | Absolute path to a folder of {spot|linear}-SYMBOL-<minute>.json.gz files copied from the private collector; Import local minutes merges them, nothing is downloaded |
How to use it
- Choose the market, symbol and last UTC day, keep 24 h for a first look, then Load history. The status line shows Downloading and reconstructing the order book… and the count of observations.
- Drag horizontally on the image to zoom in time (at least one second); double-click to return to the whole range. The footer shows the UTC time under the pointer.
- For a range covered by the private collector, paste the folder path and click Import local minutes. The report lists accepted and rejected files with the reason, the observations and the minutes merged with existing data; up to seven days ending at the imported coverage are then displayed.
- Read the coverage line before drawing conclusions from a quiet-looking area: it may be a gap.
Limits and pitfalls
- Only completed UTC days within the last nine days can be requested; the date input enforces the bounds and the screen refuses a range outside them.
- Samples are one per second and keep the peak resting liquidity of that second, so short-lived orders inside the second are compressed.
- This screen is a recorded picture of the book. It is not connected to the live heatmap, the footprint or the crypto history import of bars.
- Redistribution rights of the recorded data are not part of the product promise; the screen is an analysis tool on data the app reconstructs locally.
Related pages
- Heatmap crypto controls
- Heatmap profile window
- Liquidity heatmap explained
- Crypto orderflow footprint charts
- Crypto orderflow
This page in other languages
Frequently asked questions
- Why can I not pick today?
- Only completed UTC days are reconstructed. The date input stops at yesterday, and a window of 72 h or 168 h shifts the earliest allowed day accordingly.
- What does 'observed 71,988 of 86,400 s' mean?
- The backend measured 71,988 seconds with at least one book observation out of the 86,400 seconds requested. The rest are gaps, listed by count and largest duration; they show as blank columns.
- Can I load Binance history here?
- No. The screen is limited to Bybit Spot and Bybit USD-M Perp, three symbols, from the published archives or copied collector minutes.