Ethereum Confirmations: How Many ETH Confirmations Are Needed and Why Transactions Stay Pending
One Ethereum confirmation means your transaction has been included in a block. Each new block added after that gives it another confirmation, which means the transfer is becoming more settled on-chain. For many wallet-to-wallet ETH transfers, the first confirmation appears fairly quickly, but how many confirmations are enough depends on the receiving wallet, exchange, or app.
If your Ethereum transaction is still pending, that does not automatically mean it failed. It may simply not have been included in a block yet. And even when a transaction is confirmed on-chain, the receiver may still wait for more confirmations or complete internal processing before crediting the funds. This guide explains what Ethereum confirmations mean, how Ethereum transaction confirmation time works in practice, how to check your status with a transaction hash, and what to do if an ETH transaction seems stuck.
What is an Ethereum confirmation?
An Ethereum confirmation is the number of blocks added after the block that contains your transaction. If your transaction was included in block 100 and the network is now at block 103, your transaction has 3 confirmations.
In practical terms, the confirmation count tells you how far past initial inclusion the transaction has moved. The basic rule is simple:
- 0 confirmations usually means the transaction is still pending and has not yet been included in a block.
- 1 confirmation means it has been included in a block.
- More confirmations mean more settlement confidence for the receiver.
Wallets, exchanges, merchants, and block explorers use this count because a transaction that was just included is not treated the same way as one that has several blocks built after it.
How many Ethereum confirmations are usually enough?
There is no single number that applies everywhere. The threshold changes by use case, transfer amount, and the receiver's own crediting rule. A wallet-to-wallet transfer may be treated as effectively received much sooner than an exchange deposit.
| Situation | What is usually considered enough |
|---|---|
| Personal wallet-to-wallet ETH transfer | Often 1 confirmation plus a few more for extra confidence |
| Exchange deposit | Whatever confirmation threshold the exchange requires |
| Merchant or business payment | Usually more than a casual personal transfer, depending on risk controls |
| App or smart contract workflow | On-chain confirmation may happen first, while the app waits before updating status |
The most reliable answer is always the receiver's policy. If you are sending ETH or tokens to a platform, the important number is not what your wallet shows as "good enough," but what that platform requires before crediting the deposit.
How long do Ethereum confirmations take?
Ethereum transaction confirmation time has two parts. First, your transaction must be included in a block. After that, each new block adds another confirmation. So when people ask how long Ethereum confirmations take, they may mean either how long it takes to get the first confirmation or how long it takes to reach the receiver's threshold.
The first confirmation can be delayed by network activity and by the fee level attached to your transaction. If demand is high and your fee is too low, the transaction may wait longer before being included. If you want context on why network conditions affect timing, it helps to understand ETH gas fees before assuming the transaction is broken.
Another factor is wallet state. Sometimes the blockchain has updated, but the wallet interface has not refreshed yet. And even after the chain shows several confirmations, an exchange or app may still need additional processing time before showing the funds in your balance.
How to check Ethereum confirmations with a transaction hash
The simplest way to check ETH confirmations is to copy the transaction hash from your wallet or withdrawal page and search it in a trusted block explorer such as Etherscan. The explorer can show whether the transaction is pending, confirmed, failed, replaced, or no longer being propagated.
When checking, confirm more than just the confirmation count. Make sure the sender address matches your wallet, the recipient address matches the intended destination, and the network is correct. A common source of confusion is checking the wrong explorer for the wrong chain. If a transfer was made on a different network or a Layer 2, the transaction may not appear where you expect, which is why understanding Ethereum network vs Layer 2 can help when a payment seems missing.
If the receiving platform has a deposit threshold, compare the explorer's confirmation count with that requirement instead of relying only on your wallet's status message.
What pending, confirmed, failed, dropped, and replaced mean
These statuses do not mean the same thing, and mixing them up is one of the main reasons users think an ETH transfer has disappeared.
| Status | What it usually means |
|---|---|
| Pending | Broadcast to the network but not yet included in a block |
| Confirmed | Included in a block and gaining confirmations |
| Failed | Included on-chain, but the transaction did not complete successfully |
| Replaced | Another transaction with the same nonce was submitted and took its place |
| Dropped | The network stopped propagating the transaction, often after low-fee delay |
| Confirmed but not credited | On-chain success is visible, but the receiver has not updated your account yet |
A failed transaction is different from a pending one. Pending means it may still go through. Failed means it reached the chain but did not complete as intended. Replaced and dropped transactions usually point to fee or nonce issues rather than a problem with Ethereum itself.
Why your Ethereum transaction may stay pending
The most common reason is that the fee was not competitive enough for current network conditions. Validators generally include transactions that make economic sense first, so lower-fee transfers can wait.
Another cause is a nonce backlog. If your wallet already has an earlier pending transaction, later transactions from the same address can be held up behind it. This can make a new transfer look stuck even when the issue is actually an older transaction that has not cleared.
Pending status can also be caused by wallet sync delay or stale interface data. In those cases, one app may still show 0 confirmations while the explorer shows the transfer as confirmed. And sometimes the issue is not on Ethereum mainnet at all, but a wrong network selection, unsupported deposit network, or confusion between ETH and token transfers. If you are moving tokens and want a quick refresher on the difference, ERC20 vs ETH explains why an ETH transfer and a token transfer are not always the same thing.
What to do if an ETH transaction seems stuck
If your Ethereum transaction has been pending longer than expected, use a short troubleshooting checklist before resending anything:
- Check the transaction hash in a block explorer and confirm whether it is truly still pending.
- Verify that you are looking at the correct network and the correct recipient address.
- Compare the fee level with current network conditions if your wallet shows that information.
- Check whether an earlier pending transaction from the same wallet is blocking this one.
- Use your wallet's speed-up feature if it supports replacement with a higher fee.
- Use cancel only if the transaction is still pending and your wallet supports nonce replacement.
- If the transaction is already confirmed on-chain, review the receiver's deposit policy and wait for its internal processing.
In some cases, the practical next step is simply to wait. In others, a speed-up or replacement transaction is the right fix. The key is to diagnose the status first instead of assuming every slow transfer needs to be resent.
When the problem is not confirmations
Sometimes the chain is not the issue. A transaction can be fully confirmed on-chain while the receiving wallet, exchange, or app still shows nothing. That can happen because the receiver has not credited the deposit yet, the wallet interface has not refreshed, or the transfer was sent on a network the destination does not support.
This is also why "confirmed but not received" is not the same problem as "still pending." In the first case, the blockchain already shows success. In the second, the transaction has not been included yet. If you sent the wrong asset or used the wrong route and now need a different asset for the destination you intended, some users later choose to swap USDT to ETH, but that is separate from confirming whether the original on-chain transaction succeeded.
Do more confirmations always mean more safety?
In general, yes: more confirmations usually mean more confidence for the receiver. But that does not mean every transfer needs a long wait. For a modest personal payment, the first confirmation and a few more may be enough in practice. For a larger deposit or a business workflow, the receiver may want a higher threshold.
The confirmation count is best understood as a practical measure of settlement confidence. It is useful, but it does not replace the receiver's own rules or internal review process.