Why a Transaction Is Stuck, and What to Do

A transaction that has been sent but not confirmed is in a state that confuses people, because it looks like a completed action in a wallet and is not one on the chain. Nothing has moved. Nothing is lost either. Understanding what it is waiting for is what tells you whether to wait, act or ignore it.

Why it waits

Block space is limited and allocated by fee. A broadcast transaction sits in the mempool, the pool of pending transactions each node holds, and block producers take the most profitable ones first. A fee that was adequate when you signed can become inadequate a few minutes later if demand rises, and the transaction simply keeps waiting.

On account-based chains there is a second cause: ordering. Each transaction from an address carries a sequence number, and a chain will not process a later one until the earlier one is confirmed. One underpriced transaction can therefore block every transaction you send after it, which is why several may appear stuck when only one is the problem.

What actually fixes it

Raising the fee is the real fix. Wallets present it as speed up: the same transaction is rebroadcast with a higher fee, and producers prefer the more profitable version. Cancelling is the same mechanism pointed at nothing — a replacement that sends the funds back to yourself, which frees the sequence number for whatever comes next.

Where a wallet offers neither, the transaction will eventually confirm when demand drops, or be dropped from mempools after a period and cease to exist. Both outcomes are safe.

What does not fix it

Sending the same payment again does not replace the first one and can result in paying twice if both confirm. Contacting support cannot move a transaction; no company controls block ordering. And nobody who offers to unstick a transaction for a fee or for your recovery phrase is able to do so — that offer is the scam that attaches itself to this exact moment of frustration.