BTC: Exchange Reshuffling Ratio - Covered Exchanges
Shown as its 2019–2022 sample; the latest readings and full history are included with Pro.
How much of the covered exchanges' BTC balance moved between their own addresses over the past 7 days.
Why use it. Heavy internal reshuffling relative to reserves can mark wallet restructuring, cold-storage rotation or stress inside an exchange. How to read it. From 0 to 1: values near 1 mean as much as the whole balance moved internally in a week. A steady base level is normal deposit sweeping; read jumps with the breakdown to see which exchange is moving.
Calculation. In-house volume of all covered exchanges over the window / their summed balance at the end of the period, capped at 1. The window is 7 days: hourly values sum the 168 hours to the hour, daily values the 7 UTC days to the day, against the balance at the end of the period. In-house volume is the value an exchange pays back to its own addresses: consolidating deposits, change, and moves between hot and cold wallets. It is never counted as inflow or outflow. Computed by CryptoKeyhole from every block of its own Bitcoin node, from the same per-transaction exchange flows as the Exchange Balance and In-House Exchange Volume charts: each transaction is split by the share of its inputs each exchange funded. Periods are UTC hours and days by block header time; the latest day is a partial that updates every hour, and a period is final once six blocks follow it. Exchanges covered: those that publish their own reserve addresses (Binance, OKX, Bybit, HTX, KuCoin, Bitfinex, Crypto.com, Deribit, and BitMEX until it closed on 23 September 2026), extended with addresses our own clustering ties to them when they are spent together in consolidation transactions. Exchanges that publish no addresses, such as Coinbase and Kraken, are not covered, and customer deposit addresses are not identified, so these ratios describe the covered exchanges' known wallets rather than every exchange. Labels apply to each address's whole history, so history can change when an address list is refreshed.