Terenval Answers · P1 troubleshooting · Русская версия

Why Is My Crypto Transaction Still Pending?

A pending transaction usually means the network has seen the transaction but it has not reached the level of confirmation your wallet or recipient expects. The safest response is to diagnose the exact transaction before sending another one.

Last reviewed: 2026-10-05.

Key takeaways

• Find the transaction hash or TXID and check it independently on the correct network explorer.
• On Ethereum and EVM networks, a lower-fee transaction or a nonce gap can hold later transactions in the queue.
• On Bitcoin, an unconfirmed transaction normally remains in the mempool until a miner includes it, it is replaced, or nodes eventually stop relaying it.
• A wallet interface can lag behind the blockchain, so a stale status does not prove the transaction is lost.
• Avoid blindly resending the same transfer; duplicate payments are possible if the first transaction later confirms.

1. Start with the transaction hash, not the wallet spinner

The transaction hash is the best diagnostic anchor because it identifies the transaction at the blockchain level. Copy the hash from the wallet and open the explorer for the exact network used. Check whether the explorer says pending, confirmed/success, failed/reverted, replaced or not found.

If the explorer shows success but the wallet still shows pending, the likely problem is display, indexing or RPC refresh rather than settlement. If the explorer cannot find the transaction, verify that you are searching the correct chain. The same EVM address can exist on Ethereum, Base, Arbitrum and other networks, but transactions do not cross those chains automatically.

2. Why Ethereum and EVM transactions stay pending

Ethereum transactions are ordered by an account nonce. If transaction nonce 15 is still pending, a later transaction using nonce 16 generally cannot be finalized first. Network demand also matters: under EIP-1559 the effective fee includes a base fee and a priority component, and a transaction whose fee cap is no longer competitive may wait.

A wallet may offer a speed-up or cancellation workflow by replacing a pending transaction with another transaction using the same nonce and a higher fee. Support varies by wallet. If you do not have a clearly supported replacement action, do not manually create conflicting transactions unless you understand the nonce mechanics.

3. Why Bitcoin transactions stay unconfirmed

Bitcoin miners choose transactions from the mempool. Confirmation speed depends strongly on the transaction's fee rate relative to other transactions competing for block space. A transfer with zero confirmations has been broadcast but has not yet been included in a block.

Bitcoin blocks arrive probabilistically rather than on an exact ten-minute schedule. The Bitcoin developer guide describes roughly ten minutes as the average for a sufficiently-fee-paying transaction to receive one confirmation, not a guarantee. During congestion, a low-fee transaction can wait much longer.

4. Safe troubleshooting sequence

1. Confirm the asset and network that were actually selected.
2. Copy the transaction hash/TXID from the wallet.
3. Check that hash on the correct chain explorer.
4. Confirm the sender and recipient addresses and the transferred amount.
5. For EVM networks, look for an earlier pending nonce from the same account.
6. Check whether the wallet explicitly supports speed-up, cancel or replacement.
7. If the explorer says confirmed, give the receiving wallet, exchange or indexer time to refresh before sending again.

If the payment was sent to an exchange, a confirmed blockchain transaction can still appear pending inside the exchange because the exchange may require additional confirmations or run its own crediting/compliance checks.

Common mistakes

• Retrying the transfer before checking the original TXID.
• Looking at an Ethereum explorer for a transaction that was sent on Base, Arbitrum or BNB Smart Chain.
• Assuming a wallet's spinner is authoritative when the explorer already shows the final state.
• Increasing fees without understanding whether the wallet is replacing the same nonce or creating a second transaction.
• Treating one confirmation policy as universal across Bitcoin, Ethereum, L2 networks and exchanges.