← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · LIQUIDATION EVENTS TIMING

Crypto Liquidation Events: Event Time vs Retrieval Time

A liquidation stream message has an event time and the liquidation order's own trade time. Sampling means many events never arrive at all.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

Binance's liquidation order stream pushes at most the latest liquidation per symbol per 1000 ms, with an event time and the order's trade time. Use the order time to place the liquidation on the price chart; use event and receipt times to measure delay. Because of sampling, the absence of a message doesn't mean no liquidations happened in that second. Store connection status so disconnected periods aren't read as calm.

Which times the data carries

TimePresent?Meaning
Order trade timeYesWhen it executed
Event timeYesMessage time
Receipt timeNoRecord it
Sampling≤ 1 per symbol per secondLower-bound counts

See Crypto Liquidation Events on live data in the free ChartsPod terminal.

Open the ChartsPod terminal

What to record yourself

Field to storeWhy
order timeChart placement
event timeExchange output
received_atDelay
connected flagGap vs calm
side, qty, priceEvent detail
Liquidation Events: a stored recordLiquidation Events: a stored record: order time — Chart placement; event time — Exchange output; received_at — Delay; connected flag — Gap vs calm; side, qty, price — Event detail.order timeChart placementevent timeExchange outputreceived_atDelayconnected flagGap vs calmside, qty, priceEvent detail
Every liquidation events row carries its own clock. Original ChartsPod editorial graphic.

Example

Liquidation Events: event vs retrieval (illustrative)Liquidation Events: event vs retrieval (illustrative): T: 12:00:00.400 liquidation; SAME SECOND: Others not sent; E: 12:00:00.900 message; RECEIVED: 12:00:01.050.T12:00:00.400 liquidationSAME SECONDOthers not sentE12:00:00.900 messageRECEIVED12:00:01.050
Two clocks, one record. Original ChartsPod editorial graphic.

Illustrative: during a cascade, one message per second arrived while dozens of liquidations occurred. Timing is right for what arrived; counts are not complete.

Related: Crypto Liquidation Events: Null vs Zero - Handle Missing Fields Correctly, Liquidation Bursts on the Tape in Crypto: What Price Response Adds to the Reading.

Store connection status so disconnected periods aren't read as calm.

Test Crypto Liquidation Events on a perpetual chart; no account is needed to chart.

Launch ChartsPod

Questions readers ask

Which time places a liquidation on the chart?

The order's trade time.

Are all liquidations sent?

No; at most one per symbol per second.

Why record connection status?

To separate gaps from calm.

Sources and methodology

Field definitions come from DEX Screener's API reference and CoinGecko's onchain API documentation, read 17 October 2026. Where a schema doesn't document a timestamp, this guide says so and recommends recording retrieval time yourself.

  1. Binance USD-M: Liquidation order streams — event time and order trade time; snapshot per 1000 ms.
  2. Binance: USD-M Futures market data API — trades, depth, funding and open interest.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.