Crypto Was Sent Hours Ago—Is It Unbroadcast, Pending or Dropped?

Hours without confirmation can describe several different states. A custodial platform may not have broadcast anything, a valid transaction may be waiting in a mempool, the fee may be uncompetitive, a replacement may exist or the recipient may require more confirmations after block inclusion. Start with the transaction hash and the network, not with another transfer.

Use the Broadcast-to-Finality Clock

Every state has a different owner and remedy.

• No transaction hash: the sender or custodian has not proven broadcast
• Hash unknown to the explorer: wrong network, local-only record or dropped transaction
• Hash visible and pending: the transaction is in the network queue
• Replacement visible: a newer transaction uses the same spend or nonce
• Included in a block: blockchain confirmation has started
• Enough confirmations but no credit: the receiving service controls the next investigation

No hash means do not diagnose the mempool yet

A wallet or exchange can show sent, processing or completed before supplying a blockchain transaction ID. Without a hash, ask the sender for the selected network, processing status and broadcast record.

Use the explorer for the actual network

The same address format can appear on several EVM-compatible chains. Open the transaction hash in the explorer matching the selected network and verify sender, recipient, value, token contract, fee and status.

A pending Ethereum-style transaction may be underpriced

Ethereum.org and MetaMask explain that transactions can remain pending when the gas price or priority fee is below current demand. Wallets may offer a speed-up that resubmits the same nonce with a higher fee.

Cancellation is another replacement attempt

On supported account-based networks, a wallet can attempt to replace the pending transaction with a transaction to the sender using the same nonce and a higher fee. This works only while the original remains unconfirmed and is not a guaranteed protocol reversal.

Do not create a normal second transfer

Sending the same amount again with a new nonce does not cancel the first transaction. Both can confirm, producing a duplicate payment. Use the wallet’s documented replace, speed-up or cancel feature when appropriate.

Bitcoin uses different fee-bumping tools

Replace-by-fee can replace an eligible unconfirmed Bitcoin transaction with a higher-fee version. Child-pays-for-parent can spend an output with a high-fee child to encourage miners to include both. Availability depends on the wallet, transaction and which party controls a spendable output.

A transaction can be dropped from local mempools

Nodes do not promise to retain every unconfirmed transaction indefinitely. A low-fee transaction may disappear from an explorer or wallet after being evicted, expired or replaced. Confirm with the sender before rebroadcasting.

Pending dependencies can block later transactions

On nonce-based networks, a later transaction from the same account can wait behind an earlier nonce. Replacing or resolving the oldest pending transaction can be necessary before newer ones proceed.

Custodial withdrawals add a processing clock

FaucetPay currently states that Normal withdrawals are batched, Priority withdrawals are individual and pending requests can also reflect network congestion or internal verification. Its help centre recommends review and support when a withdrawal remains pending longer than expected.

Block inclusion is not the receiver’s finality rule

An exchange or payment service can require several confirmations before crediting a deposit. The explorer may show success while the receiver still waits for its defined confirmation count.

Use the Pending Transaction Evidence Pack

Save the transaction hash, network, sender, recipient, amount, fee or feerate, nonce or RBF status, first-seen time, current explorer state, replacement hash and receiving-service requirement.

Worked ownership diagnosis

An exchange withdrawal has no hash after three hours: the exchange owns the delay. An Ethereum transaction has a hash and remains pending with a low priority fee: the sender wallet may offer speed-up. A Bitcoin transaction is RBF-enabled and underpriced: the sender can consider an RBF bump.

Do not pay strangers to accelerate the transaction

A legitimate wallet can show supported fee-bumping controls. Never send a separate crypto payment, share a recovery phrase or grant remote device access to someone claiming they can confirm the transfer.

Current conclusion

A delayed transaction is solved by state and ownership. Find the hash, confirm the network, identify whether it is unbroadcast, pending, replaced, dropped or already included, and use only the tool supported by that network and sender.

Evidence boundaries

Ethereum.org and MetaMask documentation supports nonce-based speed-up and cancellation behavior. Bitcoin Optech documents RBF and CPFP. Custodial platforms can add their own processing and confirmation requirements.

Pending-transaction sources — July 29, 2026

Primary network, wallet and FaucetPay documentation was prioritized.

• Ethereum pending transaction FAQ: https://ethereum.org/community/support/faq/
• Ethereum transaction lifecycle: https://ethereum.org/developers/docs/transactions/
• MetaMask speed-up and cancel guide: https://support.metamask.io/manage-crypto/transactions/how-to-speed-up-or-cancel-a-pending-transaction/
• Bitcoin Optech replace-by-fee: https://bitcoinops.org/en/topics/replace-by-fee/
• Bitcoin Optech child-pays-for-parent: https://bitcoinops.org/en/topics/cpfp/
• FaucetPay pending withdrawal guidance: https://faq.faucetpay.io/knowledge-base/withdrawal-stuck-in-processing/

FAQ