Independent · Read only · 64 verified tokens
What happened in the hour after the Binance exploiter sold?
We anchored every token to its first observed DEX sale and measured the matching Binance USDT-M Futures move over the next 60 minutes.
Explore all 64 tokens ↓Bottom line
48 of 64 tokens were lower 60 minutes after the first observed sale. The equal-weighted move was −3.16%.
48 lower16 higher / flat
Strong co-movement, not proof that the hacker caused the full decline.
FULL RANKING
Best 60m → worst 60m
All 64 tokens use one fixed anchor and horizon: first observed sale → 60 minutes. Click any ticker to open its path and Etherscan transaction.
METHODOLOGY
One reproducible rule for every token
- 01
Find the first tracker-observed Sell (DEX) transaction for each token.
- 02
Set the completed 1-minute close immediately before that sale minute to 0%.
- 03
Measure the matching Binance USDT-M perpetual path from the sale minute through +60 minutes.
- 04
Keep only direct, identity-verified underlyings with estimated total sales of at least $500,000.
Read this before interpreting the chart
Sale values are tracker estimates based on current prices, not reconstructed DEX execution proceeds.
The first-sale minute close can include movement before and after the exact transaction within that minute.
Many tokens were sold during overlapping periods, so the observations are not independent.
Hack news, broad market moves and derivatives positioning may also explain part of the decline.