An exchange tells you your deposit address has been updated. If you are still watching the net flow of that old address on an on-chain analysis platform, the data is basically wrong. This distortion cannot be avoided—once the old address stops being used, historical inflow numbers become frozen, and all future consolidation moves will create a bunch of "fake outflows." But you can fix it by merging addresses and calibrating consolidation transactions.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
Why does an old address become misleading? Exchanges change deposit addresses all the time, whether for key rotation, security upgrades, or wallet architecture adjustments. After the change, the old address goes through one or more fund consolidations—all assets are moved to the exchange's main wallet or a new hot wallet. After that, the address never receives normal user deposits again. If your dashboard only monitors that single address, you will see a sudden giant outflow one day, and then inflows drop to zero. People who don't understand this often misread it as "a whale withdrawing and running away" or "the project team dumping" and make bad decisions.
To get historical net flow that is not distorted by address updates, you need to do address merging manually. The steps below are directly usable.
Step 1: Pin down the last active block of the old address
Go to a block explorer (Etherscan, Solscan, etc.) and open the deposit address you are tracking. Find the last "normal small deposit" transaction—usually around the time the exchange announced the address change.
How to do it: On the address page under "Transactions," look at incoming transfers (In) in reverse chronological order and ignore the very large consolidation transaction. A common pattern: right before the consolidation, there are many scattered transfers of varying amounts—those are the last batch of real user deposits. Find the latest transaction among that batch and record its timestamp and block height.
Completion standard: You have a rough cutoff—for example, "after 14:32 UTC on January 20, 2025, this address no longer receives normal deposits." This will serve as the dividing line when you split analysis into old and new phases later.
Step 2: Trace the consolidation flow and find the new monitoring target
Once the old address is retired, the exchange consolidates the funds. You need to find where they went.
How to do it: On the same block explorer, check the outgoing (Out) records of the old address. Usually you will quickly see one or more out transactions, and the output address is often the exchange's consolidation wallet (or a new hot wallet). Note down this new address.
Completion standard: You now have a set of new addresses: at least one consolidation address that received most of the old address's balance. Copy its address.
Case A: You only want to see the overall net flow of a token on an exchange
In this case you cannot just monitor user deposit addresses; you need to watch the exchange's known deposit and hot wallet addresses together. Search the consolidation address in the tag system of Etherscan or similar tools (or on platforms like Arkham or Nansen). If it already has an "Exchange Wallet" label, use it directly. No label? Use the pattern you identified in Step 1 to verify in reverse: consolidation addresses typically keep receiving consolidations from other deposit addresses and rarely send small outgoing transactions.
Case B: You built a query or dashboard on Dune / Flipside
Directly in your SQL query, wrap the old and new addresses using WHERE "from" IN ('old_address', 'old_address2', 'consolidation_address', 'new_deposit_address') OR "to" IN (...), replacing the logic that only monitored a single address. Then rerun it and check whether the net flow curve connects smoothly.
Step 3: Adjust the net flow algorithm on your analysis platform
Even after merging addresses, you must manually remove the "fake outflows" caused by consolidation transactions. Otherwise net flow will suddenly show a sell pressure that never existed.
How to do it:
- Find the transaction from the old address that swept the entire balance and mark it as an internal transfer.
- Exclude this transfer when calculating net flow for that wallet.
- If you use Dune, you can filter out the consolidation tx_hash with a CASE WHEN; if you use a front-end product like Nansen where you cannot directly change the algorithm, look for views like "Net flow without internal transfers," or add an "Internal" tag to the consolidation address in your labels.
Completion standard: After correction, the net flow at the moment the old address was retired should not show a cliff-like drop. It should continue smoothly, showing you successfully removed the mechanical disturbance caused by the address change.
Common cause of failure: Mistaking consolidation for dumping
Many people doing on-chain analysis set off alarms: a wallet related to an exchange suddenly moves out millions of USDT. But if you click into it and see that the sending address had just stopped receiving user deposits right before that, it is most likely consolidation, not a withdrawal. Ignoring this background and posting bearish calls on social media often leads to embarrassment. So you must set a condition in your monitoring script: if an address has had no small, random incoming transfers for N consecutive hours and then suddenly shows an outgoing transaction close to its entire balance, classify it as suspected consolidation first and do not count it directly as a net outflow.
Risk note: Even if you judge it as consolidation, that does not mean there is no selling pressure in the market—if the destination address of the consolidation later shows frequent distributions to market maker wallets or transfers into DEX pools, that is the real signal to watch. You just cannot use a single consolidation from the old address as the reason. The correct approach is to trace the full fund path for at least two hops and confirm whether the final destination is an exchange hot wallet or a DEX liquidity pool.
If you have not done a small test transaction with this exchange to label addresses before, you can register an account, use a platform referral code to make a very small deposit to get the latest deposit address, and then add that address into your monitoring set so your data does not break the next time they change it.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
FAQ
Q1: Can the old deposit address still receive coins? Can I recover them?
After most exchanges change the address, the old one will stop automatic crediting. Policies vary widely: for example, after Binance changes deposit addresses for certain tokens, the old address is disabled; funds will not be credited automatically, and you need to submit a ticket for recovery, which may involve a processing fee (this statement remained valid as of February 2025). After OKX changes an address, some old addresses may still support automatic crediting for a period, but the platform strongly recommends using the new address. Always check the latest deposit page of the platform before sending funds.
Q2: Can smart money platforms that track total inflows and outflows (like Nansen) automatically detect address updates?
Not fully automatically. Address labels on platforms like Nansen are maintained by humans or heuristic algorithms. After an exchange updates addresses at scale, labels can lag by hours to days. If you rely on indicators like "Smart Money inflow to exchanges," you must pay attention to the label update time, or the data during that period will also be distorted. During the delay, you can manually cross-check on Arkham or a block explorer.
Q3: How to handle multi-chain scenarios?
You need to apply the methods in Steps 2 and 3 separately for each chain. The same exchange's Ethereum deposit address and Solana deposit address are changed independently, and their consolidation paths do not cross. Mixing up chains will directly introduce unaligned data into your analysis.
Now, open your corrected dashboard or query and observe the net flow curve across the time point of the address change. If everything is done correctly, you should see a smooth cumulative net inflow/outflow trend with no artificial gap. If there is still an unexplained sudden change, go back to the block explorer and verify whether that address had secondary consolidations that were not merged. The whole process, from adjusting the query to confirming data continuity, usually takes no more than one refresh cycle.
