edgedepthEARLY ACCESSSign in
Menu
Terminal
Recent moves
ResearchResearch hubResearch WorkbenchInvestigate a moveLiquidation mapsPublished reportsDaily movesEvent archiveSaved studiesLive alertsMarketsData coverage
LearnGuidesReading libraryWorked examplesGuided lessonsFAQ
DevelopersAPI documentationMCP setupConnect an AI agentOpen source
Pricing
< All conditions
Condition · recorded history

At least $5M liquidated in one hour

Observed liquidation notional over the trailing one-hour window is at least $5 million.

What is a liquidation?

Recorded window: 5 Oct 2026 to 3 Nov 2026 (UTC). Counted 4 Nov 2026 at 08:13 UTC.

Read it in context

  1. On one market

    Each market page compares that market with its own minutes, not with every market at once.

    Compare markets

  2. Test it, then plan it

    Narrow it to your markets and dates in the Workbench. A tested result leads to Plan a trade, which measures what trading it would have paid after costs.

    Edit this test in Workbench

By market

Results vary by market. Compare a market before drawing a conclusion.

Most matches:BTCUSDTETHUSDT
How results varied by market

Range across 2 markets with at least 30 measured: reached +5% within 24 hours in 0 of 34 on BTCUSDT (0%) to 1 of 31 on ETHUSDT (3%).

Every market pooled, without context

What happened in the next 24 hours?

Both moves were less common than on minutes without it.

Other minutes are the same markets and dates without this condition. Each percentage is the share of measured minutes that reached that move from the starting price.

Price touched +5% or higher

When this held
6.0% · 5 of 83 minutes
Other minutes
24.4% · 5,062,974 of 20,742,078 minutes

Price touched −10% or lower

When this held
2.4% · 2 of 83 minutes
Other minutes
8.6% · 1,789,735 of 20,742,078 minutes

Price can touch both levels within the same 24 hours.

Every matching minute counts, so one long run adds many near-identical minutes. Busy markets weigh most.

Every condition is measured over the same 24 hours, whatever the length of its own reading. Other windows and move sizes shows shorter and longer windows.

This counts how often price touched a level, not what trading it would have paid.

Sample and counting

Rates use the 83 of 85 matches, pooled across 523 markets, with a full 24 hours after them. The 2 newer ones are left out, not counted as zero.

When it happened
Matches per UTC day, 2026-10-05 to 2026-11-04

About 2.7 a day, on 24 of 31 days: spread through the record rather than one event.

Other windows and move sizes
Matches that reached each move within each window. Counts first; the measured row is what each rate is over.
Move1 hour4 hours24 hours72 hours7 days
Measured8383838064
Too recent222521
+0.1% or more71 (85.5%)72 (86.7%)77 (92.8%)75 (93.8%)60 (93.8%)
+0.2% or more61 (73.5%)66 (79.5%)72 (86.7%)72 (90.0%)57 (89.1%)
+0.5% or more32 (38.6%)51 (61.4%)63 (75.9%)63 (78.8%)57 (89.1%)
+1% or more12 (14.5%)24 (28.9%)46 (55.4%)49 (61.3%)50 (78.1%)
+2% or more5 (6.0%)11 (13.3%)26 (31.3%)34 (42.5%)37 (57.8%)
+5% or more0 (0.0%)1 (1.2%)5 (6.0%)8 (10.0%)13 (20.3%)
+10% or more0 (0.0%)0 (0.0%)0 (0.0%)1 (1.3%)3 (4.7%)
+15% or more0 (0.0%)0 (0.0%)0 (0.0%)0 (0.0%)2 (3.1%)
+20% or more0 (0.0%)0 (0.0%)0 (0.0%)0 (0.0%)1 (1.6%)
−0.1% or lower74 (89.2%)76 (91.6%)79 (95.2%)78 (97.5%)64 (100.0%)
−0.2% or lower62 (74.7%)72 (86.7%)76 (91.6%)76 (95.0%)63 (98.4%)
−0.5% or lower45 (54.2%)60 (72.3%)74 (89.2%)74 (92.5%)63 (98.4%)
−1% or lower25 (30.1%)45 (54.2%)63 (75.9%)68 (85.0%)62 (96.9%)
−2% or lower6 (7.2%)18 (21.7%)42 (50.6%)56 (70.0%)59 (92.2%)
−5% or lower0 (0.0%)1 (1.2%)9 (10.8%)20 (25.0%)32 (50.0%)
−10% or lower0 (0.0%)0 (0.0%)2 (2.4%)3 (3.8%)3 (4.7%)
−15% or lower0 (0.0%)0 (0.0%)1 (1.2%)1 (1.3%)1 (1.6%)
−20% or lower0 (0.0%)0 (0.0%)0 (0.0%)0 (0.0%)1 (1.6%)

Each window counts only matches old enough for it, so a longer window can show fewer.

Distributions and daily counts
Upside reached · 24hUpside reached (MFE, 24h)The most price moved up within 24 hours of each match: a high-water mark, never a close. 83 with a complete 24 hours.
Drawdown · 24hDrawdown (MAE, 24h)The worst price moved against within 24 hours of each match: the deepest point, never the close. 83 with a complete 24 hours.
Price 30 minutes laterForward 30-minute returnForward 30-minute returns across 83 matches: 61% of them finished up. 2 too recent.

How to read a distribution

Matches per UTC day

  • 5 Oct1 match
  • 6 Oct0 matches
  • 7 Oct5 matches
  • 8 Oct16 matches
  • 9 Oct0 matches
  • 10 Oct0 matches
  • 11 Oct2 matches
  • 12 Oct6 matches
  • 13 Oct5 matches
  • 14 Oct2 matches
  • 15 Oct5 matches
  • 16 Oct3 matches
  • 17 Oct2 matches
  • 18 Oct2 matches
  • 19 Oct1 match
  • 20 Oct1 match
  • 21 Oct0 matches
  • 22 Oct4 matches
  • 23 Oct2 matches
  • 24 Oct5 matches
  • 25 Oct1 match
  • 26 Oct1 match
  • 27 Oct1 match
  • 28 Oct2 matches
  • 29 Oct9 matches
  • 30 Oct6 matches
  • 31 Oct0 matches
  • 1 Nov0 matches
  • 2 Nov2 matches
  • 3 Nov1 match
  • 4 Nov0 matches
How this is counted
  • Each rate counts only matches with the full window after them.
  • A minute where a reading was missing is left out and reported, not read as zero.
  • The condition picks the setup, never the outcome: a definition that filters on what followed is rejected (OUTCOME_IN_PREDICATE). Every match is measured, winners and losers alike.
  • "Other minutes" is every other eligible minute in the same markets and window. It is a reference, not a control group.
  • "Reached +5%" uses the highest price inside the window (maximum favourable excursion, MFE); "fell to −10%" uses the lowest (maximum adverse excursion, MAE). Neither is the close.
  • Checked 22,589,783 eligible market-minutes (eligible_symbol_buckets) on 523 markets, 2026-10-05 00:00 to 2026-11-04 00:00 UTC.
  • These counts pool every market, so markets that match often weigh more. Each market page compares that market with its own reference.
  • Live status is not connected yet, so this page is recorded history only.

What are MFE and MAE?

Reproducibility key (q#dd52adab)

The key that re-runs this exact count. Same key, same bytes; when the record grows, the dataset revision changes.

grammar
research_query.v2
normalization
archive_normalization.v1
feature library
feature_defs.v1
dataset revision
cc2519aaced62c8f3946a5c8e8c146365a36bcf89acc64808f1dcba916d48aca
query hash
dd52adab84ff4dc2770a29313f74faa352af65ba393738d608faebc04f8dae12
scanned window
2026-10-05T00:00:00.000Z to 2026-11-04T00:00:00.000Z (UTC)

Re-run over the API

The exact search definition behind this count. Send it to the key-authed research API (or the MCP research tool) and compare the bytes; a cached rerun is free.

{
  "schema_version": "research_query.v2",
  "normalization_version": "archive_normalization.v1",
  "feature_version": "feature_defs.v1",
  "target": "record_occurrences",
  "where": {
    "all": [
      [
        "feature.liq_notional_usd_1h",
        "gte",
        5000000
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-10-05T00:00:00.000Z",
          "2026-11-04T00:00:00.000Z"
        ]
      ]
    ]
  },
  "sort": [
    "times.anchor_time",
    "desc"
  ],
  "page": {
    "limit": 50,
    "cursor": null
  }
}
curl -s https://app.edgedepth.com/api/v1/research/query \
  -H 'authorization: Bearer $EDGEDEPTH_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"schema_version":"research_query.v2","normalization_version":"archive_normalization.v1","feature_version":"feature_defs.v1","target":"record_occurrences","where":{"all":[["feature.liq_notional_usd_1h","gte",5000000],["times.anchor_time","between",["2026-10-05T00:00:00.000Z","2026-11-04T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'

Past examples from the record, not a guarantee or a prediction. Nothing here is trading advice.