Deposit sent to an old or regenerated address
A deposit address is a pointer an exchange recorded against an account at a moment in time. Many platforms later issue a new address for the same asset, close an account, or recycle an address after inactivity. The chain does not know any of that.
The transfer can confirm to an address the platform still controls, an address it used to control, or an address that never belonged to the account you think it did. Those three cases look identical in a wallet history and are not identical to support.
What usually causes this
These are the common explanations for this category of problem. Which one applies to your transfer depends on your transaction, the network it used and the destination's deposit rules — that is what the check above works out.
- The sending wallet reused a previously copied exchange address after the platform rotated it
- The destination account was closed, restricted or migrated
- The address was generated for a different asset or network than the one you sent
- A bookmarked address belonged to a different person, sub-account or deleted login
What the transaction can prove, and what it cannot
A TXID proves the network, the amount, the destination string and whether the transfer succeeded. It cannot prove which customer account an exchange currently binds to that string. That binding lives in the platform's database.
This is why 'the explorer shows it arrived' is true and 'it is not in my balance' can also be true. Support is being asked to re-bind a payment, not to reverse a chain.
| Situation | On-chain appearance | Usual next step |
|---|---|---|
| Address still belongs to your live account | Payment to a platform-controlled address | Uncredited-deposit or delayed-credit case; send the hash once |
| Address was yours, then rotated | Same: payment to an address the platform likely still sweeps | Coinbase Exchange documents that old generated addresses remain associated; other platforms may still need a ticket |
| Account closed or offboarded | Payment to an address that may still be swept into omnibus wallets | Reopen or prove former ownership; recovery is a support policy, not automatic |
| Address never belonged to you | Payment to someone else's deposit or a contract | Only the controller of that address can move it; a second send will not help |
- Coinbase Exchange: why crypto addresses change — Official Exchange note that new addresses are generated for privacy and that previously generated addresses remain associated with the account.
- Coinbase Exchange: generating deposit addresses — Official guidance that funds sent to an old Exchange address are still processed if the address was generated for that account.
Self-custody is a different problem with the same search query
People also search this phrase after sending to an old hardware-wallet receive address. On Bitcoin and Ethereum, previous receive addresses usually still spend from the same wallet if you still hold the seed. That is not an exchange recovery case.
The dangerous overlap is a seed-phrase phishing site that offers to 'restore the old address'. A legitimate diagnosis of an exchange deposit never needs the seed. A legitimate restore of your own wallet happens in the wallet vendor's software, not in a Telegram chat.
How to talk to the exchange without making it worse
A TXLens diagnosis can show whether the destination is consistent with a known platform deposit pattern and which official route to use. It cannot reassign an address inside Binance, Coinbase or Kraken.
- Send one ticket with the TXID, asset, network, amount, the address you used, and the date you copied it.
- Say that you sent to a previously generated deposit address, not that the chain failed.
- Do not generate a new deposit and send a second payment 'to the new address' hoping it will pull the first one across.
- If the platform publishes a recovery form, use that instead of a free-text chat.
Old address versus unsupported network
If you are not sure whether the problem is a rotated address or a network the platform does not credit, run the policy checker first. An old Coinbase Exchange address can still be valid; a TRON USDT send to Coinbase is a different category.
- Policy checker for a suspected stale deposit address — Compares platform, asset and network. The TXID still has to prove where the payment landed.
What you get, and what it costs
Free, always
The transaction check: network, asset, amount, both addresses, timestamp, on-chain status, confirmation count, and a copyable evidence message for support. No diagnosis.
£9.99, one-off
The diagnosis: the likely cause, recovery outlook, step-by-step instructions, the official support route, wording written for that case, and 72-hour monitoring. No subscription.
Questions
If I sent to an old Binance or Coinbase address, is the money gone?
Not necessarily. Many platforms still control retired deposit addresses and can credit them after a support review. Some do not, especially after an account is closed. The TXID establishes that the payment arrived; only the platform can say whether it will re-bind it.
Should I send the same amount again to the new address?
No. A second transfer is a second deposit. It does not move the first one, and if the first address is no longer yours you now have two problems.
Related
Platform requirements on this page were last reviewed 2026-08. They change without notice, which is why every diagnosis is phrased as a likely cause rather than a certainty.
TXLens is read-only. We only use your transaction ID and public blockchain data. We never ask for your private keys, seed phrase or exchange login.