poolcod
A crypto liquidation map tool should do more than place bright horizontal bands around a candlestick chart. It should explain the origin of every layer, keep confirmed events separate from estimates and provide enough historical and multi-exchange context to evaluate whether a visible zone is still relevant.
Start with data provenance
Ask where each value comes from. Real liquidations should originate from exchange streams or documented endpoints. Their side, price and quantity must be normalized carefully because exchanges do not always use the same field names or side conventions. An interface that calls every plotted level a real liquidation is making a claim it cannot support.
Estimated pools require a different description. A model can use OHLC candles, traded volume, open interest, taker flow and leverage assumptions to infer regions of sensitivity. That can be useful, but it remains an estimate. The platform should never suggest that it has access to private account entries or every trader's exact margin settings.
Check the historical model
A useful map preserves how zones evolved over time. Historical persistence helps distinguish a concentration that survived several market rotations from one created by a brief burst of activity. It also lets the analyst study whether similar zones were absorbed, rejected or crossed during a cascade.
Historical depth must be interpreted honestly. Older candles can support a longer modelled context, while real liquidation records are limited to the events actually collected and stored. Backfilling real events from candles would be an estimate and must not be presented as exchange-reported history.
Evaluate filters and visual scale
Timeframe, exchange, side and intensity controls should answer specific questions. A scalper may need nearby zones and recent events. A swing trader may care more about persistent concentrations across higher timeframes. The color scale should adapt without making weak levels look as important as the strongest visible areas.
Thin lines can preserve price precision, but they should become readable at the current zoom level. Dense heatmaps also need a sensible threshold so that smaller pools remain available without turning the entire chart into one saturated block. Reliability is not the same as showing every calculated row at maximum brightness.
Look for multi-layer confirmation
The tool should let you compare the map with price structure, volume, open interest and taker flow. A large upper pool below a rejected resistance has a different meaning from the same pool after the market accepts above that resistance. If buying aggression rises but price does not advance, absorption may matter more than the pool's color.
A practical evaluation checklist
Confirm that real and estimated data can be toggled independently. Check whether the exchange and market are identified. Review the methodology and limitations. Verify that historical navigation does not invent information beyond the collection window. Test whether zones update when the timeframe or symbol changes and whether loading states prevent the user from reading stale data as current.
Finally, judge whether the map supports conditional scenarios rather than automatic signals. A good tool makes uncertainty visible. It shows where leverage may become fragile, what has already been liquidated and which evidence would strengthen or invalidate the current interpretation.