A pending Ethereum transaction has been submitted but has not yet reached a confirmed onchain result. Before trying to resend, speed up or cancel anything, check the transaction hash in a block explorer and confirm whether the network actually sees it as pending.
A transaction that is already confirmed cannot be cancelled or reversed by changing the gas fee. A failed, dropped or locally displayed transaction can require a different response, so status diagnosis comes first.
Wallet interfaces can lag or keep old local state, so use the transaction hash as the reference. Open the hash in a compatible block explorer and compare the explorer status with what the wallet displays before taking advanced action.
| Status | What it means | What to do next |
|---|---|---|
| Pending | Submitted but not yet included/finalized | Wait, or consider a wallet-native speed-up/cancel option |
| Confirmed / success | Included successfully | Do not try to cancel; the transaction is final |
| Failed | Included but execution failed | Review the failure and gas before resubmitting a new transaction |
| Dropped / not found | Not currently visible as an active network transaction | Refresh wallet/provider state and investigate before sending a duplicate |
Closing and reopening the wallet application can clear a stale interface display, but it does not cancel a transaction that is actually pending on the network.
A common cause is a fee that is no longer competitive with current network demand. Nonce ordering can also create a queue in which a later transaction waits behind an earlier pending transaction from the same account.
| Cause | How it can create a delay |
|---|---|
| Low effective fee | Validators may prioritize transactions offering more competitive fees |
| Sudden network demand | A fee that looked reasonable when submitted can become less competitive |
| Earlier nonce still pending | Later transactions from the same account normally wait for the earlier nonce |
| Wallet/provider issue | The wallet can display stale local state or fail to broadcast as expected |
| Competing replacement | Two transactions using the same nonce can compete until one is accepted |
For the fee mechanics behind inclusion priority, see Ethereum gas fees explained.
Waiting is reasonable when the transaction is not urgent and the fee may become acceptable as network conditions change. If the wallet offers a Speed up function, it generally creates a replacement transaction using the same nonce but a higher fee so the replacement can be selected first.
Speeding up costs more because the replacement needs to be more competitive. Use the wallet's built-in option when available rather than manually guessing nonce and fee values unless you understand replacement transactions well.
A speed-up does not mean two successful transfers should occur. Transactions with the same nonce compete, and once one is accepted the other cannot also use that nonce successfully.
A wallet's Cancel function is also a replacement strategy. It attempts to submit another same-nonce transaction, often back to your own account, with a fee designed to be processed before the original pending transaction.
Cancellation can only be attempted while the original transaction is still pending. If the original confirms first, the blockchain result stands and the cancellation attempt cannot reverse it.
For that reason, treat cancel as an attempt rather than a guarantee. Always recheck the explorer status before assuming the original transaction has disappeared.
Each transaction from an Ethereum account has a nonce that orders it relative to other transactions from that account. If nonce n remains pending, a transaction using nonce n+1 normally cannot simply jump ahead and finalize first.
| Transaction | Example status | Effect |
|---|---|---|
| Nonce 42 | Pending | Blocks normal progression to later nonces |
| Nonce 43 | Submitted later | Waits behind nonce 42 |
| Replacement nonce 42 | Higher-fee speed-up/cancel attempt | Competes with the original nonce 42 transaction |
Advanced wallets can expose custom nonce controls, but manual replacement should be treated as an expert option. Fix the oldest pending nonce first and prefer built-in wallet tools when they are available.
Repeated trial-and-error can turn one delayed transaction into several confusing wallet entries. Check the onchain state first and avoid actions that create new security or accounting problems.
If the transaction was a normal wallet transfer, the ETH sending guide explains the original transfer flow and tracking basics.
When an ETH deposit to Swap-ETH.io remains pending, service processing cannot begin as if the deposit were already confirmed. First determine the blockchain status using the transaction hash, then keep the order ID and transaction hash together for support if the onchain deposit confirms but the service status does not update as expected.
Do not automatically create a second order or send a second deposit just because the first transaction is slow. If the blockchain transaction is still pending, use wallet-native speed-up or cancellation tools where appropriate; if the transaction has confirmed and the service status is the problem, contact Swap-ETH.io Support with the order details.
Support can investigate the service-side order state, but it cannot force Ethereum validators to confirm a pending network transaction.
There is no universal maximum that applies to every wallet and provider. A transaction can remain pending while its fee is uncompetitive or while an earlier nonce blocks it.
You can attempt to cancel it with a same-nonce replacement while it is still pending. Cancellation is not possible after the original transaction has confirmed.
It resubmits a replacement using the same nonce with a more competitive fee. The goal is for the replacement to be included before the original pending transaction.
Only the transaction that is ultimately included consumes execution gas for that nonce. Wallet interfaces can still show multiple attempts or estimates, so check the final onchain result.
It is the sequence value used to order transactions sent from an Ethereum account. A lower pending nonce can block later transactions from progressing normally.
No. Once confirmed successfully, it cannot be cancelled by submitting a replacement. Recovery requires a new transaction from the recipient if they are willing and able to return funds.
Check the deposit transaction hash first. If it is pending, resolve the blockchain transaction; if it is confirmed but the order has not updated, contact support with the order ID and transaction hash.