ONUSDT rose 72% into Jul 28. The record covers the whole lead-up.
Move window: 2026-07-28 05:00 to 2026-07-28 22:00 UTC. The record for ONUSDT currently ends 2026-08-04 00:00 UTC.
Counted on 2026-08-05, against a record covering to 2026-08-04 00:00 UTC. These numbers are frozen: this page will always say what it said the day it was written.
Book imbalance · top levels ≤ -0.58 and Containment · 15m inside and Sweep + reclaim · 1h bearish
feature.book_imbalance + feature.candle_containment_15m + feature.candle_sweep_reclaim_1h
Read at 1 hour before the move.
Minutes like this appeared 39 times in the 43,201 minutes searched (<0.1%). What followed leaned up: 22 of the 39 matches with a complete 30 minutes forward rose (56%).
Of the 39 fires, 32 came before the move began and 1 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 1.3 a day, on 21 of 31 days: spread through the record rather than one event.
q#412e636c @ dataset 461da594
Best supported: Book imbalance · top levels ≤ -0.58 and Containment · 15m inside and Sweep + reclaim · 1h bearish, the combination with the most fires before the move began.
Opens this exact search in the research tool. Nothing runs until you confirm it there, and arming it as an alert sends a message when it next becomes true.
Picked in hindsight: the counts include every other time these readings appeared, not just this move.
Also counted
This is not a similarity search. Each count matches the exact readings above and nothing else.
Book imbalance · top levels ≤ -0.96 and Sweep + reclaim · 1h bearish and VWAP distance · day ≥ 0.053
feature.book_imbalance + feature.candle_sweep_reclaim_1h + feature.vwap_dist
Read at 1 minute before the move.
Minutes like this appeared only 17 times in the 43,201 minutes searched. What followed was close to a coin flip: 8 rose and 9 fell over the next 30 minutes (17 of the 17 matches have a complete 30 minutes forward).
Of the 17 fires, 12 came before the move began and 2 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 0.5 a day, on 8 of 31 days: spread through the record rather than one event.
q#7b2abe70 @ dataset 461da594
Sweep + reclaim · 1h bearish and Return · 15m ≤ -0.019 and Return · 1h ≤ -0.034
feature.candle_sweep_reclaim_1h + feature.ret_15m + feature.ret_1h
Read at 15 minutes before the move.
Minutes like this appeared only 12 times in the 43,201 minutes searched. What followed was close to a coin flip: 6 rose and 6 fell over the next 30 minutes (12 of the 12 matches have a complete 30 minutes forward).
Of the 12 fires, 8 came before the move began and 1 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 0.4 a day, on 8 of 31 days: spread through the record rather than one event.
q#6840fd0e @ dataset 461da594
Fires often arrive as clusters of consecutive minutes, and forward windows overlap. A cluster is one episode, not many independent trials.
If these counts read weaker than the move suggested, that is the tool working: the lead-up of a picked move always looks special until it is counted everywhere else.