ETH sent but not received
ETH on Ethereum, ETH on Base and ETH on Arbitrum are the same asset on different networks with the same address format — which makes an L2 mismatch easy to create and easy to overlook.
TXLens identifies which network the transaction actually ran on.
Where ETH is credited, by network
ETH exists on several networks and every platform picks its own subset. A transfer over a network outside that subset confirms perfectly and is never credited, which is why "I definitely sent it" and "they definitely have not received it" are both true at once.
| Platform | Networks credited | Approximate minimum |
|---|---|---|
| Binance | Ethereum, Base, Arbitrum One and OP Mainnet | 0.0001 ETH |
| Coinbase | Ethereum, Base, Arbitrum One and OP Mainnet | 0.00001 ETH |
| Kraken | Ethereum, Base, Arbitrum One and OP Mainnet | 0.005 ETH |
| Crypto.com | Ethereum, Arbitrum One and OP Mainnet | 0.001 ETH |
| Bybit | Ethereum and Arbitrum One | 0.01 ETH |
| OKX | Ethereum, Base, Arbitrum One and OP Mainnet | 0.01 ETH |
| KuCoin | Ethereum, Arbitrum One and OP Mainnet | 0.01 ETH |
| Revolut | Ethereum | 0.001 ETH |
Approximate, reviewed 2026-08.
Confirmations required, platform by platform
The same transfer is 'not yet confirmed enough' at one platform and long since credited at another, because the threshold is a business decision rather than a property of the network. Comparing them is the quickest way to see whether your wait is normal.
| Platform | Bitcoin | Ethereum | TRON | Polygon | Solana |
|---|---|---|---|---|---|
| Binance | 1 | 6 | 1 | 100 | 32 |
| Coinbase | 3 | 35 | 1 | 200 | 32 |
| Kraken | 4 | 20 | 20 | 120 | 32 |
| Crypto.com | 1 | 12 | 1 | 100 | 32 |
| Bybit | 1 | 6 | 1 | 100 | 32 |
| OKX | 1 | 12 | 1 | 100 | 32 |
| KuCoin | 2 | 12 | 1 | 100 | 32 |
| Revolut | 3 | 30 | 20 | 150 | 32 |
Approximate, reviewed 2026-08. A dash means the platform does not credit deposits on that network, or does not publish a figure.
Could this be a wrong-network ETH transfer?
A successful ETH transaction can still be invisible to the destination when it arrived on a network that destination does not credit. The transaction ID proves which network was used; recoverability then depends on who controls the receiving address there.
- Check whether crypto sent on the wrong network can be recovered — Identify the network used before contacting the destination.
- Compare the asset and network with published exchange recovery routes — A policy match is guidance, not a guarantee that a specific transfer will be recovered.
Where the platform deposit figures come from
- Binance support centre
- Coinbase support centre
- Kraken support centre
- Crypto.com support centre
- Bybit support centre
- OKX support centre
- KuCoin support centre
- Revolut support centre
Policy snapshot 2026-08; verify in-account.
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
I sent ETH from an L2 to an exchange and nothing arrived. Why?
Most likely the exchange credits ETH deposits on Ethereum only, or on a different set of L2s. The address is valid on every EVM chain, so nothing stops the transfer from succeeding on the wrong one.
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.