Crypto Orderflow Charts: Footprint, Delta and Heatmap
Crypto orderflow charts describe executions and displayed liquidity on a particular exchange and market. A Bitcoin spot footprint, a perpetual-futures footprint and a heatmap of resting orders are different datasets. Choose the venue and contract before comparing the signals.
Senzoukria · Learn · Updated 13 September 2026
Footprint versus heatmap: executed and resting volume
| View | Inputs | Reading |
|---|---|---|
| Footprint | Trade price, quantity and classified aggressor | Volume executed at each price |
| Cumulative delta | Classified trades and a reset convention | Accumulated buy-aggressor minus sell-aggressor volume |
| Liquidity heatmap | Order-book snapshots and updates | Displayed resting size over time |
The footprint reading guide explains the cells; the heatmap guide explains the book. A bright band is displayed liquidity, not proof that its owner will keep it there.
Start with the exchange, then spot or perpetual
“BTC volume” is incomplete without a venue, pair, market type and unit. BTC/USDT spot trades and a BTC perpetual contract can have different activity at the same instant. A single exchange view is not the entire crypto market.
Before comparing charts, align the interval, timezone, price bucket size and quantity unit. Base-asset quantity, quote-currency notional and contract counts are not interchangeable. A merged chart must explain how it converts them.
Bid, ask and delta: a worked example
Suppose a spot footprint cell records 1.2 BTC sold aggressively into the bid and 2.0 BTC bought aggressively at the ask. Its total executed quantity is 3.2 BTC and its delta is +0.8 BTC. Every execution still has a buyer and seller: the sign classifies who took liquidity.
Providers encode that side differently. Binance documents a buyer-is-maker flag: if the buyer is the maker, the seller is the aggressor. Bybit documents the taker side on its public trade stream. Verify the mapping before comparing delta values.
Trade aggregation also matters: Binance’s aggregate-trade stream groups executions associated with a single taker order. A displayed event count therefore need not equal a raw execution count.
Historical trades are not historical depth
A footprint can be built from suitably classified trade history. A historical heatmap needs book data for the period, including updates between snapshots. Trade archives cannot reveal an order that appeared and was cancelled without trading.
Do not combine Binance trades and a Bybit book as if they were one exchange’s matched event history. Record coverage separately for each source. Missing intervals are unknown observations, not zero liquidity or zero trading.
Free data, software cost and live availability
Public data access and software licensing are separate questions. Check the venue’s access conditions, network availability and historical coverage. The free footprint comparison distinguishes free demonstrations, licence tiers and data access.
Senzoukria provides analysis paths for supported Binance spot/perpetual and Bybit data. Availability depends on the selected source and instrument; historical depth coverage must be checked for the requested dates. These analysis connections do not establish Binance or Bybit order routing or crypto autopilot support.
A first reading session
- Select one exchange and one exact instrument.
- Confirm the quantity unit and aggressor convention.
- Read one footprint bar: total volume, delta and price progression.
- Compare the same interval with the book only if depth was recorded.
- Record observations and counterexamples before proposing a strategy.
Use the footprint workspace and heatmap overview to understand the two displays. If you want to test a rule, continue to quant trading for beginners; an attractive chart alone is not a backtest.
Frequently asked questions
- What is a crypto orderflow chart?
- It displays executed trades or order-book activity for a specified crypto venue and instrument. A footprint groups executions by price; a heatmap shows displayed order-book depth over time.
- Why do Bitcoin footprint charts differ between exchanges?
- Each exchange has its own trades, order book and instrument definitions. Spot and perpetual contracts also differ. Aggregated products require explicit choices about venues, units and synchronization.
- Can free crypto data produce a footprint chart?
- Public exchange trade feeds can provide inputs for footprint calculations, subject to access and coverage. That does not make every charting application free, and historical depth is a separate dataset.
- Can historical trades recreate a liquidity heatmap?
- No. Trades show executions, while a heatmap needs the resting book and its updates. Missing past limit orders and cancellations cannot be recovered from trade prints alone.