Most stuck transactions just need more time. Under 15 minutes, wait. Longer than that, or no transaction hash at all, match your symptom below.
Find your symptom
What you're seeing | What it means | Go to |
The ENS App keeps spinning and my wallet shows a Pending transaction | Pending in the mempool: gas fee likely too low | Pending for too long |
I'm stuck on "Almost there" mid-registration | The ENS App lost track of the commit hash | Stuck on "Almost there" |
I can't see the transaction hash anywhere, or Etherscan says it doesn't exist | Wallet-connection issue: never broadcast | Not on Etherscan |
Etherscan says Success but the ENS App hasn't updated | Confirmed onchain: refresh the ENS App | Already confirmed |
If you're not sure which case you're in: copy the transaction hash from your wallet's activity log and paste it into Etherscan. What it shows points you to one of the four sections.
Good to know
A pending transaction is one your wallet broadcast and the network has accepted but not yet included in a block. Most confirm in 1–2 minutes; busy networks can take 5–15 minutes or longer.
Speeding up or cancelling both replace the original transaction using the same nonce; neither double-spends.
Both speed-up and cancel still cost gas. The original transaction's gas isn't refunded.
Pending for too long (the most common case)
If Etherscan shows your transaction as Pending and it's been under 10 minutes, give it more time: busy networks routinely take 5–15 minutes to include a transaction.
If it's been longer than 10–15 minutes, the gas fee is probably too low. You have two options: speed up (pay more gas) or cancel (drop it for a small fee).
Speed up in MetaMask:
Open MetaMask and find the pending transaction under Activity.
Click the transaction, then Speed up.
Pick a higher gas fee and approve in your wallet.
Cancel in MetaMask:
Open the pending transaction under Activity.
Click Cancel and approve the $0 replacement.
Other wallets have the same controls under different labels.
Important: don't speed up the commit transaction during .eth registration (Step 1 of 3). The ENS App tracks a hash stored in your browser; replacing the commit strands your registration on "Almost there". If the commit is slow, wait it out. See Fix .eth registration errors.
Stuck on "Almost there"
Try this first: disconnect your wallet, close the page, reopen app.ens.domains in the same browser, and reconnect. It's free and it often works. If the registration comes back at Step 3, finish it.
Don't clear site data or switch browsers yet — that can destroy the commit code the app needs.
If it doesn't come back, the ENS App has lost the commit hash it saved in your browser. That usually happens when the commit transaction was sped up or replaced, or after a browser refresh cleared local storage. What you can do next depends on your commit transaction — work through the Stuck on "Almost there" section in Fix .eth registration errors. If the commit can't be recovered you'll need to register again, and its gas isn't refundable.
Not on Etherscan
If Etherscan can't find the hash, the transaction never reached the network. That's a wallet-connection issue, not a transaction issue. Your wallet logged the action but didn't broadcast it. Common causes:
MetaMask Smart Transactions intercepting the send.
A dropped link between MetaMask and a hardware wallet.
The wallet recording the transaction in its history without actually broadcasting it.
See Why won't my wallet connect or broadcast my ENS transaction? for the fix.
Already confirmed
If Etherscan shows Success but the ENS App still looks stuck, the transaction landed onchain. The ENS App just hasn't picked it up. Refresh the page. If it still doesn't update, sign out of the wallet, disconnect, and reconnect.
Cached sites like Etherscan and OpenSea read records on their own schedule and can sometimes take a day or two to reflect a change. That's downstream of the ENS App and separate from the ENS App not refreshing.