Why Is My Transaction Stuck?

A stuck crypto transaction means a wallet, exchange, DEX, bridge, claim page, token page, or blockchain app appears unable to finish a transaction. The user may see “pending,” “queued,” “submitted,” “processing,” “waiting for confirmation,” “stuck,” “speed up,” “cancel,” “replacement underpriced,” or a transaction hash that does not seem to reach a final confirmed, failed, dropped, or replaced state. For the beginner concept, read Why Is My Transaction Pending?.

This issue matters because a stuck transaction can block later actions from the same wallet, especially on networks where transactions are processed in nonce order. A stuck transfer, approval, swap, bridge, claim, or contract call may be caused by low gas, network congestion, an older pending transaction, delayed wallet data, a failed broadcast, a wrong network check, or an app-specific processing delay. For network context, read What Is a Blockchain Network?.

This guide will help you check whether the transaction is really stuck on-chain, confirm the correct network and explorer, understand gas and nonce problems, decide whether to wait, speed up, cancel, replace, retry, or stop, and avoid unsafe wallet prompts. The goal is not to click every fix button. The goal is to verify the transaction state before signing another request.

Quick fix answer

A crypto transaction is usually stuck because the gas fee is too low, the network is congested, a previous nonce is blocking the wallet queue, the wallet or RPC endpoint is delayed, the transaction was not broadcast correctly, or the user is checking the wrong network. The safest first step is to open the transaction hash on the correct block explorer and review status, nonce, gas fee, sender, recipient, contract interaction, and final result before retrying.

Fast checklist: Copy the transaction hash, confirm the network, open the correct explorer, check whether the transaction is pending, failed, dropped, replaced, or missing, review nonce and gas, avoid duplicate transfers, and never enter a seed phrase into any page claiming it can “unstick” the transaction.

Simple example: You submit a token transfer and the wallet keeps showing “pending” for a long time. Before sending again, check the transaction hash on the correct explorer. If the explorer shows the transaction is pending, the issue may be gas, congestion, or nonce order. If the explorer cannot find it, the wallet may not have broadcast it or you may be checking the wrong network.

Before you try to fix it

Many stuck-transaction problems look urgent, but not every stuck status needs immediate action. Some transactions confirm after waiting. Some fail and only spend gas. Some are replaced by a newer transaction. Some are dropped by the network. Some never reached the blockchain and are only stuck inside the wallet interface. The correct block explorer is the best starting point.

A safe fix starts with observation, not repeated clicking. Do not instantly send the same transfer again, approve a new contract, sign a recovery message, or follow a support link from a social media reply. First identify whether the transaction exists on-chain, which network it belongs to, whether it is still pending, and whether another transaction from the same wallet is blocking it. For source safety, read How to Check Official Links.

Why this problem matters

A stuck transaction can affect more than one action. If an older transaction from the same wallet is pending, later swaps, approvals, transfers, claims, bridge transactions, or cancellations may also wait behind it. Users often try to fix the newest action, even though the oldest pending transaction is the one blocking the queue.

The larger risk is that users may react too quickly and create a second problem. Fake support pages often target people with stuck transactions. They may ask users to validate a wallet, pay an unlock fee, connect to a recovery tool, sign a message, approve a contract, or enter a seed phrase. A normal transaction fix should not require secret wallet information. If a page or person asks for secrets, review How to Avoid Crypto Scams before continuing.

Useful next step: If gas, explorers, networks, and nonce order feel confusing, read What Is Blockchain? and Why Wallet Network Matters first. Stuck transaction fixes depend on knowing where the transaction was actually broadcast and how the wallet queue works.

The basic fix idea

The safest way to troubleshoot a stuck transaction is to separate wallet display from on-chain state. A wallet may show a pending or queued status because it remembers a submitted request. The explorer may show whether the transaction is truly pending, already confirmed, failed, replaced, dropped, or missing entirely. The correct fix depends on that difference.

1. Confirm the network first

Start by checking the network selected in the wallet or app. A transaction on Ethereum, BNB Smart Chain, Base, Arbitrum, Polygon, Solana, Tron, or another network must be checked on the matching explorer. Searching a transaction hash on the wrong explorer can make a valid transaction look missing. For a full network explanation, see Why Wallet Network Matters.

2. Check the transaction hash on the correct explorer

Open the transaction hash on the explorer for the actual network. Check the status, confirmations, timestamp, sender, recipient, nonce if shown, gas fee, gas limit, contract interaction, token transfer events, and any error text. If the explorer shows no transaction, the wallet may not have broadcast it, the hash may belong to another network, or the interface may be delayed.

3. Look for an older pending nonce

On many account-based networks, transactions from the same wallet are processed in order. If an older transaction is pending with a lower nonce, later transactions may wait behind it. In that case, retrying the latest action may not fix the queue. The older pending transaction may need to confirm, be replaced, be cancelled, or be dropped.

4. Choose wait, speed up, cancel, replace, or stop

If the network is simply congested, waiting may be enough. If the fee is too low, some wallets allow a speed-up or replacement transaction. If the transaction is unwanted and still pending, some wallets allow a cancel attempt. These actions should be done only after verifying the transaction on the correct explorer. For the detailed flow, read How to Speed Up a Transaction.

Common causes

Stuck transactions usually come from gas fee settings, network congestion, nonce order, delayed wallet or RPC data, wrong explorer checks, failed broadcast, replacement rules, app-side processing, bridge relays, or unsafe recovery pages. Each cause has a different safe response.

Cause 1: Gas fee is too low

If the transaction fee is not competitive for current network conditions, the transaction may stay pending. Some wallets allow users to speed up or replace a pending transaction by submitting a new transaction with the same nonce and a higher fee. Do not use random “gas fix” websites that ask for wallet secrets.

Cause 2: Network congestion

When many users are sending transactions at the same time, validators or block producers may prioritize transactions with more competitive fees. A lower-fee transaction can remain pending longer than expected. This does not automatically mean funds are lost, but it should be checked on the correct explorer before retrying.

Cause 3: Previous nonce is blocking the wallet

A wallet may have an older pending transaction that blocks newer transactions from confirming. This can make a later transfer, swap, approval, claim, or bridge action look stuck even though the older transaction is the real queue problem. Check recent transactions from the same wallet address.

Cause 4: Wallet or RPC endpoint is delayed

Sometimes the transaction has already confirmed, failed, dropped, or been replaced, but the wallet or RPC endpoint still shows pending. Refreshing the wallet, checking the correct explorer, switching networks carefully, or waiting briefly may clarify the state. Avoid signing new requests only because one interface looks delayed.

Cause 5: Transaction was not broadcast

A wallet may show a submitted or queued transaction even though it never reached the network. This can happen if the app failed before broadcasting, the wallet lost connection, the RPC rejected the transaction, or the user rejected the final prompt. If the correct explorer cannot find the hash, the transaction may not be live on-chain.

Cause 6: Wrong network or wrong explorer

A transaction can look missing or stuck if the user checks the wrong network. The selected wallet network, transaction hash, explorer, token contract, and app should all refer to the same chain. If the wrong network was used, read What to Do If You Used the Wrong Network.

Cause 7: Swap, bridge, claim, or app-side processing is delayed

Some actions have more than one step. A bridge can be confirmed on the source chain while still waiting for destination-chain relay. A swap can wait before execution. A claim page can wait for contract confirmation or indexing. Check the transaction hash and any official status page before submitting another action.

Cause 8: Transaction was replaced or dropped

A stuck transaction may be replaced by another transaction using the same nonce, or it may be dropped by the network if it remains unattractive or unbroadcast long enough. The wallet may not update instantly. The explorer and wallet history can help show whether the original transaction was replaced, dropped, or still pending.

Cause 9: A fake support page is pretending to fix it

Fake support pages may claim that a stuck transaction needs wallet validation, seed phrase entry, a special unlock fee, or a recovery signature. These are serious warning signs. A real stuck transaction fix does not require sharing private keys, seed phrases, recovery phrases, or secret phrases.

How to apply the fix in practice

Use this process before retrying, cancelling, replacing, or sending another transaction. It is designed for global users across different wallets, networks, explorers, DEXs, bridges, claim pages, and blockchain apps. The exact interface names may vary, but the verification logic is the same.

Copy the transaction hash: Use the hash from the wallet, app, exchange withdrawal page, DEX, bridge, claim page, or explorer.
Confirm the network: Check which chain the transaction belongs to, including the network name, gas token, and explorer.
Open the correct explorer: Search the hash on the matching explorer and check whether it is pending, confirmed, failed, dropped, replaced, or missing.
Review transaction details: Check sender, recipient, nonce if available, gas fee, gas limit, contract interaction, token transfer events, and timestamp.
Check for older pending transactions: Review recent transactions from the same wallet address to see whether a lower nonce is blocking the queue.
Choose the safest next step: Depending on the state, wait, speed up, cancel, replace, refresh the wallet, change RPC carefully, or stop using the suspicious page.
Do not create duplicates blindly: Avoid sending the same transfer again until you know whether the original transaction is live, replaced, dropped, confirmed, or missing.
Verify after action: After speeding up, cancelling, replacing, retrying, or waiting, check the explorer again and confirm the final status.

Related guide: If you need to replace a low-fee pending transaction, read How to Speed Up a Transaction. If the explorer shows a failure after the stuck status ends, read How to Read Transaction Error Messages.

Detailed troubleshooting checklist

This checklist helps separate a truly stuck on-chain transaction from a wallet display delay, wrong network, failed broadcast, nonce queue, replacement, dropped transaction, app-side processing, or unsafe support page.

Transaction hash: Use the hash to check whether the transaction is pending, confirmed, failed, dropped, replaced, or missing.
Network: Confirm the chain name, chain ID if shown, native gas token, explorer, and wallet network selection.
Wallet address: Make sure the sender address is the same wallet that submitted the transaction.
Recipient or contract: Check whether the transaction is a transfer, approval, swap, bridge, claim, contract call, or cancellation.
Nonce: If available, check whether an older transaction from the same wallet is blocking later transactions.
Gas fee: Review whether the transaction fee looks low compared with current network conditions shown by the wallet or explorer.
Explorer status: Do not rely only on the wallet popup. Compare wallet status with the correct explorer.
App status: If the transaction belongs to a bridge, swap, claim, or exchange withdrawal, check the official app status only from verified links.
Wallet request: Before speeding up, cancelling, replacing, or retrying, read the wallet prompt and confirm the network and action.
Result: After any fix, verify the final state in both the wallet and the correct explorer.

What not to do

A rushed stuck-transaction fix can create a bigger problem than the delay. The goal is not to click every button until the wallet changes. The goal is to understand whether the transaction is actually stuck, why it is waiting, and which minimal action is safest.

Do not enter a seed phrase, private key, recovery phrase, or secret phrase into any website that claims it can unstick a transaction.
Do not send the same transfer again before checking whether the original transaction is still pending, confirmed, dropped, replaced, or missing.
Do not approve unrelated token spending while trying to fix a stuck transfer, swap, bridge, or claim.
Do not trust direct-message support accounts that ask for wallet validation, unlock fees, remote access, or recovery phrases.
Do not assume the wallet display is always current. Check the correct explorer before acting.
Do not cancel or replace a transaction unless you understand which pending transaction and nonce the wallet is trying to modify.
Do not send funds to “activate,” “release,” “unlock,” or “confirm” a stuck transaction.

Common mistakes

Stuck transaction troubleshooting is confusing because wallets compress technical state into short labels. A user may see a pending badge, gas fee, transaction hash, explorer page, or app status and assume it proves more than it actually proves. Safer troubleshooting means checking the same transaction from the wallet, explorer, and official app source when relevant.

Mistake 1: Checking the wrong explorer

A transaction must be checked on the explorer for the network where it was submitted. Searching a BNB Smart Chain transaction on an Ethereum explorer, or a Tron transaction on an EVM explorer, can make the transaction look missing even when it exists.

Mistake 2: Sending a duplicate transfer too soon

Sending again before understanding the original transaction can create extra fees, duplicate transfers, nonce conflicts, or more stuck transactions. First check whether the original transaction is live on-chain and whether it can be safely replaced or cancelled.

Mistake 3: Ignoring an older pending nonce

If an older transaction from the same wallet is still pending, later transactions may wait behind it. Users often try to fix the latest action even though the older transaction is the one blocking the queue.

Mistake 4: Confusing wallet delay with network delay

A wallet may continue showing stuck or pending after a transaction already confirmed, failed, dropped, or was replaced. When the wallet and explorer disagree, use the correct explorer as an important reference and refresh the wallet state carefully.

Mistake 5: Trusting fake transaction recovery tools

Some fake pages claim they can recover, unlock, synchronize, or manually confirm stuck transactions. Be cautious if a fix requires seed phrases, private keys, remote access, broad approvals, upfront fees, or unclear signatures.

Mistake 6: Assuming stuck means funds are lost

A stuck transaction is not the same as a confirmed loss. It may confirm, fail, be dropped, or be replaced. The transaction result and token transfer events determine what actually happened.

When to be extra careful

Some stuck transaction fixes deserve extra caution because the next action can expose funds, permissions, account history, or future token access. Slow down if the fix requires a new wallet signature, spending approval, contract interaction, bridge action, claim action, replacement transaction, or cancellation transaction.

Before speeding up: Confirm the transaction hash, network, nonce, fee replacement behavior, and that the wallet is modifying the intended stuck transaction.
Before cancelling: Confirm that the transaction is still pending and that the cancel attempt uses the correct network and wallet.
Before retrying a transfer: Confirm the original transaction is not still pending or already confirmed.
Before approving a new request: Check whether the wallet prompt is a transfer, approval, signature, network switch, or contract interaction.
Before using a support link: Verify the official website, documentation, support portal, and domain spelling.
Before sending more gas: Confirm that the destination, network, and action are legitimate. Do not send funds to “unlock” a transaction.

How to know the fix worked

A stuck transaction fix is complete only when the final state is clear. The explorer should show whether the transaction confirmed, failed, dropped, or was replaced. The wallet should eventually match that state. If the transaction belonged to a swap, bridge, approval, claim, or transfer, the related token movement or contract event should also be checked.

For confirmed transactions: The explorer should show a confirmed block, timestamp, sender, recipient, and relevant transfer or contract events.
For failed transactions: The explorer should show a failed or reverted status, and the intended transfer or contract result may not have completed.
For replaced transactions: The explorer or wallet should show that another transaction with the same nonce replaced the original.
For dropped transactions: The transaction should no longer be pending, and the wallet queue should stop blocking later actions.
For wallet display delays: The wallet should update after refresh, network check, RPC update, or app resync, while the explorer remains the key reference.

FAQ

Why is my crypto transaction stuck?

A crypto transaction may be stuck because the gas fee is too low, the network is congested, an older nonce is blocking the wallet, the RPC endpoint is delayed, the transaction was not broadcast, or the transaction is being checked on the wrong network. Start by opening the transaction hash on the correct explorer.

Is a stuck transaction the same as a pending transaction?

They are closely related, but “stuck” is a broader user-facing term. A stuck transaction may be truly pending on-chain, blocked by an older nonce, delayed by a wallet or RPC issue, dropped, replaced, failed, or never broadcast. The explorer helps separate these cases.

How long can a transaction stay stuck?

It depends on the network, fee settings, wallet behavior, and whether the transaction remains valid in the network's transaction pool. Some stuck transactions confirm after a delay, some are replaced, and some are dropped. The explorer and wallet history can help identify the current state.

Should I retry a stuck transaction?

Not immediately. First check whether the original transaction is live on the correct explorer and whether it is pending, confirmed, failed, dropped, replaced, or missing. Retrying too quickly can create duplicate transfers, nonce issues, or unnecessary fees.

Can I speed up a stuck transaction?

Sometimes. Some wallets allow a pending transaction to be replaced with a higher-fee transaction using the same nonce. Confirm the network, transaction hash, and wallet prompt before doing this. Read How to Speed Up a Transaction for the detailed flow.

Can I cancel a stuck transaction?

Sometimes, if the transaction is still pending and the network and wallet support a cancellation-style replacement. A cancel attempt is usually another transaction, so it can also require gas and may fail if the original confirms first. Check the explorer before trying.

Why does my wallet show stuck but the explorer says confirmed?

The wallet may be delayed, cached, or connected to a slow RPC endpoint. If the correct explorer shows the transaction is confirmed, use that as an important reference and refresh the wallet carefully. Also check whether the expected token transfer or contract event actually happened.

Why does the explorer not find my stuck transaction hash?

You may be checking the wrong network, the transaction may not have been broadcast, the wallet may have only queued it locally, or the hash may belong to another chain. Confirm the selected wallet network, app history, and correct explorer before retrying.

Did I lose funds because the transaction is stuck?

A stuck transaction does not automatically mean funds are lost. The final status matters. It may confirm, fail, be dropped, or be replaced. Check the explorer for token transfers, contract events, gas used, and final status.

What if a website says I must enter my seed phrase to unstick it?

Do not enter a seed phrase, private key, recovery phrase, or secret phrase into any website. A normal stuck transaction fix should not require wallet secrets. Treat that request as a serious warning sign and review How to Avoid Crypto Scams.

Related concepts

This fix connects to several beginner crypto concepts. Reading these pages can help users understand why stuck transaction troubleshooting depends on the correct network, explorer status, gas fee, nonce order, wallet prompts, token contracts, and official source verification.

Summary

If your crypto transaction is stuck, the safest response is to check the transaction hash on the correct block explorer before retrying. A transaction may be stuck because of low gas, network congestion, nonce order, wallet or RPC delay, wrong explorer checks, bridge or app processing, or a transaction that was never fully broadcast. The correct next step depends on whether the transaction is truly pending, already confirmed, failed, replaced, dropped, or missing from the explorer. If it is stuck because the fee is too low, a speed-up or replacement may be possible through the wallet. If an older nonce is blocking the queue, the older pending transaction may need attention first. If the wallet and explorer disagree, use the correct explorer as an important reference and refresh the wallet carefully. Never enter a seed phrase, private key, or recovery phrase into a website claiming it can fix a stuck transaction.

The safest troubleshooting habit is to verify before acting. Check the network, transaction hash, wallet address, nonce, gas fee, wallet request, and final explorer result before approving another action. This reduces the chance of using the wrong network, trusting a fake support page, sending a duplicate transaction, approving an unsafe spender, or repeating a transaction unnecessarily.

Eonwell does not recommend any specific wallet, token, exchange, protocol, service, or transaction. This page is for neutral crypto education only.

Topics