
An unconfirmed transaction refers to a blockchain transfer that has been broadcast to the network but has not yet been included in a block.
This means the transaction has been sent by a wallet or node and is currently waiting in the network’s mempool (memory pool) until it is selected by miners or validators for inclusion in a block. Until that happens, it remains “unconfirmed.” Once confirmed, the transaction’s block height and transaction hash can be tracked on block explorers, and platforms typically require a certain number of “confirmations” before crediting the funds.
The main factors influencing confirmation speed include transaction fees (gas fees), network congestion, priority settings, and node policies. The higher and more appropriate the fee—aligned with current network recommendations—the more likely the transaction will be included in the next few blocks.
Understanding unconfirmed transactions helps users avoid the anxiety and risks of funds “stuck in transit.”
When withdrawing from exchanges or making on-chain transfers, transactions that remain unconfirmed for long periods may result in missed deposit opportunities, lost trading entries or exits, price slippage, or even additional losses. In DeFi platforms, unconfirmed actions could prevent timely loan repayments, exposing positions to liquidation risk during volatility.
For NFT minting or participating in hot token launches, unconfirmed transactions may lead to missing out on minting spots or sudden price changes, resulting in outcomes that differ significantly from expectations. For merchants or teams, delayed confirmations can disrupt fund management and reconciliation processes.
The process follows this flow: broadcast → queue → selected for block inclusion → confirmation.
After being broadcast, transactions enter the mempool—a temporary waiting area similar to a train station where all pending transactions queue up. Miners or validators act like ticket inspectors, prioritizing transactions that offer higher rewards (fees).
Gas fees determine transaction priority. On Ethereum, gas fees consist of a base fee plus a priority fee (tip for block producers); higher priority fees increase the likelihood of inclusion in the next block batch. On Bitcoin, wallets estimate fees per byte—higher fees boost selection chances.
If a transaction gets stuck, some chains and wallets offer acceleration features. Bitcoin supports RBF (Replace-By-Fee), allowing users to resend a transaction with a higher fee to replace the previous one. CPFP (Child-Pays-For-Parent) lets users create a child transaction with a high fee to incentivize miners to include both transactions together. Ethereum wallets often provide “speed up” or “cancel” options, resending the same transaction with a higher priority fee.
Once written into a block, explorers display the confirmation count—the number of blocks added after the transaction’s block. More confirmations mean a lower chance of reversal and greater security.
The most common indicators are statuses like “Pending,” “Confirming,” or “Waiting for Block.”
On exchanges such as Gate, withdrawing BTC will display “Submitted, Confirming” and note that “X confirmations” are required before funds are credited. Different coins and networks have varying confirmation requirements; for example, BTC usually needs several confirmations, while account-based chains like ETH set their own thresholds according to platform policies.
For on-chain interactions, wallet interfaces often show transactions as “Pending.” On explorers like Etherscan or OKLink, the transaction hash page will show “Pending,” along with current gas conditions and estimated confirmation time. During popular NFT mints or new token launches, the number of pending transactions can spike dramatically.
For cross-chain bridges and layer 2 networks, processes continue only after source chain confirmations are complete. For example, bridging from Ethereum mainnet to Arbitrum requires mainnet confirmation before subsequent proof or settlement steps occur.
Key strategies include increasing your chance of being included in a block, avoiding congestion, and using appropriate tools.
Over the past year, network congestion has become more event-driven and structurally dispersed.
Public monitoring for Q3 2025 shows that during Bitcoin inscription booms and peak volatility, unconfirmed transactions have surged to hundreds of thousands at their peak but drop sharply during quieter periods. On Ethereum, during bursts of token or NFT activity, priority fees frequently spiked above 150–300 gwei (and sometimes even higher), while off-peak lows dropped below 20 gwei.
Layer 2 networks like Base and Arbitrum continue to relieve mainnet pressure—these networks’ growing activity has shortened average daily mainnet congestion periods. Now, average unconfirmed wait times depend more on “hot events” than on continuous all-day congestion.
Compared to 2024, spikes in fees and congestion are now concentrated in fewer windows of heightened activity. Wallets and platforms now provide more timely fee estimates, reducing the average duration of stalled transactions overall. However, differences across chains and times remain significant—always refer to real-time explorer or platform information.
These are distinct concepts: one describes transaction status; the other measures security.
An “unconfirmed transaction” means it is still queued in the mempool and has not yet been added to a block. The “confirmation count” refers to how many new blocks have been built on top of the block containing your transaction—the higher this number, the harder it is to reverse.
Platforms typically specify how many confirmations are required before crediting funds. The time from “unconfirmed” to “confirmed” depends on network congestion and your fee settings; reaching the required confirmation count takes additional blocks being added after inclusion.
No. Unconfirmed transactions typically stay in the mempool while awaiting inclusion in a block. If they are not picked up after a prolonged period—often due to low fees—they may be purged from the network or require rebroadcasting. Most often, if your fee is too low relative to network conditions, your transaction may be dropped within hours or days. Setting an appropriate gas fee or using acceleration services helps ensure timely processing.
Your funds remain in your wallet in a “pending spend” state—they have not actually left your account yet nor arrived at the recipient’s address. During this period you may not see the balance available for spending, but it also hasn’t reached its destination. Once confirmed in a block, the transfer is completed.
In some cases, yes. On Ethereum you can send a new transaction with zero value or a higher gas fee to the same address—this may overwrite the original pending transaction. On Bitcoin, you’d need either a double-spend attempt or wait for expiration (usually around 7 days). Cancellation is not always guaranteed; if congested, using exchange-provided acceleration tools such as Gate’s is generally more effective.
Main causes include low gas fees, network congestion during peak times, node failures or unstable connections. Incorrect recipient addresses or wallet sync delays can also slow down confirmation. Always check your status via block explorers (like Etherscan), and consider increasing your gas fee or rebroadcasting if needed.
Unconfirmed transactions themselves do not directly compromise account security—but extended delays may indicate wallet or network issues. Critically, always verify recipient addresses before sending—a confirmed transaction cannot be reversed. Stick to reputable platforms such as Gate and use hardware wallets where possible; always confirm every address carefully to guard against fraud.


