Transfer stuck pending: sort out which kind of stuck before you touch anything

You hit send, and the transaction sits there marked pending. A minute, ten minutes, half an hour — the line doesn't move, and nothing has shown up at the other end. The two things people reach for first, refreshing the page over and over and googling "how to speed up," are both beside the point.

Draw the boundary before anything else. If the explorer shows your transaction already in a block and the confirmation count is just climbing, that isn't stuck, that's the normal wait — how long a deposit takes covers the per-chain ballpark. If the confirmations are well past the requirement and Binance still hasn't credited it, that's a different problem — work through confirmations done but not credited. This piece handles one case only: the transaction has never been mined into a block and is still hanging there.

Four kinds of stuck that look identical

"Pending" in a wallet interface is a very coarse word covering at least four different states. Take the TXID to a block explorer and check three things — can it be found, does it have a block number, and what does the status say — and they come apart:

• The explorer can't find the TXID at all. It probably never broadcast, or the network has already dropped it. It isn't queuing; it isn't there.
• It's there, marked pending or unconfirmed, with no block number. That's the case this guide is about: the transaction is waiting in the network's queue and no block has picked it up yet.
• It has a block number and the confirmation count is climbing. It went through; it's just accruing confirmations. Leave it alone.
• It has a block number but the status reads failed. That one is over — the coins didn't move, though the fee may still have been charged. Find out why it failed and send again, rather than waiting on it.

Worth adding: on Etherscan you may also see a transaction marked as dropped, or dropped and replaced. That's the explorer telling you it's out of the queue — a replacement with the same nonce won, or the network let it go. Either way, stop waiting on that hash. For a sense of how many confirmations each chain needs once you're in a block, see the confirmations reference by chain.

Who signed it decides whether you can touch it

Once you've established it really is queuing, don't go hunting for a speed-up button yet. There's a more important question: who signed and broadcast this transaction? The answer decides whether you hold any cards at all.

• Your own wallet sent it (MetaMask, Rabby, a Ledger — anything where you hold the key). You have room to act; on some chains you can push a replacement transaction over it. More on that below.
• It's a withdrawal from Binance — the page says sent, the chain shows nothing. This one isn't yours to touch. The exchange's wallet signed and broadcast it, you don't hold that key, so speeding up, cancelling or re-pricing are all off the table. What you can do is gather the withdrawal record, TXID, network, amount and rough time and take it to official support. And if the withdrawal is still marked under review with no transaction on-chain yet, that's an earlier stage entirely — see how long a withdrawal review takes.
• You're the recipient (someone is paying you, or you're waiting on a deposit into Binance). Also not yours to touch. Only the sending side can replace a transaction; you can wait, or go chase them.

Change chains and "pending" changes meaning

Pending means quite different things depending on where the transaction lives. Knowing which chain you're on tells you whether waiting is even useful.

• Ethereum, BSC, Arbitrum and other EVM chains: it really is a queue. There's a pool of candidate transactions, they get picked by what they bid, and a low bid can wait indefinitely. These chains add a trap that's easy to miss: transactions from one address carry a sequence number (nonce), and until the earlier one lands, everything behind it waits too. So while you stare at the newest transaction, the one actually blocking the road may be an older one. List that address's pending transactions by nonce, lowest first, and deal with the front of the line. On why the price swings so much, see what gas actually is.
• Bitcoin: also a queue, priced per virtual byte (sat/vB). A low fee rate during a busy stretch can leave a transaction hanging for a long time. Whether you can fix it depends on whether the original opted into RBF, whether your wallet offers a fee bump, or whether you can use CPFP with a spendable child output. Those are not EVM nonce replacement. Use only options your wallet actually provides, not an unverified "accelerator" page.
• Tron: not an EVM-style fee auction. TRON's transaction lifecycle says a broadcast transaction that passes node validation enters a cache pool, then block producers take transactions in arrival order. If it hangs, first confirm it really broadcast; if it is on-chain but failed, read the transaction receipt and error first. Resource shortage is only one possible cause: insufficient Bandwidth or Energy without enough TRX to pay, FeeLimit, parameter validation, or contract execution can all affect the result.
• Solana: if it's hanging, it's probably gone. Transactions here carry a recent blockhash with a short validity window; once that lapses the network stops accepting it, and your wallet may show a failure or simply nothing. So "stuck for hours" on Solana usually isn't a queue at all — it's a transaction that expired. Look up your address's recent history on an explorer and confirm whether it ever happened.

Three things worth doing, three to avoid

Once the diagnosis is done, there really aren't many moves. The useful ones:

1. Establish the status before you touch anything. Take the TXID to the right explorer — Etherscan for Ethereum and its family, BscScan for BSC, Tronscan for Tron, mempool.space for Bitcoin — and settle those three questions: findable, block number, status. Skip this and everything after it is guesswork.
2. Only consider replacement on an EVM chain that supports account-nonce replacement. The transaction must come from your own wallet, and that wallet must explicitly offer "speed up" or "cancel." Speed-up normally resends with the same nonce and a higher fee; cancel uses that nonce for a zero-value transaction to yourself. Both cost a fee and can fail. Bitcoin uses RBF or CPFP instead, while Tron and Solana do not inherit this EVM procedure. Once the original is mined, replacement is no longer available.
3. When the whole network is expensive, waiting is a move. Congestion isn't personal. Once fee levels come down, transactions that were stuck at the back often get picked up on their own. Bid higher only if you genuinely can't wait.

The ones to avoid:

• Don't pay a third-party "transaction accelerator." All you need is a resend at a higher price, and that lives in your own wallet. Those pages charge for nothing at best, and at worst want you to connect a wallet and sign an approval you can't read.
• Don't give anyone your seed phrase, private key or 2FA codes. No legitimate process needs them to "unstick" anything. Anyone asking is running a scam.
• Don't keep hitting send. Tapping again because nothing moved can leave you with two live transactions, or a longer nonce queue to untangle.

FAQ

Sources checked 2026-07-30: Ethereum transactions, MetaMask pending transactions, Bitcoin Core bumpfee, TRON transaction lifecycle, TRON resource model, and Solana confirmation and expiration. Check live status with Etherscan, BscScan, Tronscan, or mempool.space; for exchange-side steps, use the current Binance Help Center. Fees, congestion and inclusion times remain live data.