Bitcoin Fees Suddenly High: Should You Send Now or Wait?
Whether to send now or wait depends on how much you're willing to pay for time and how urgent the transaction is.
Bitcoin transaction fees (miner fees) are determined by on-chain congestion. During a week in early July 2026, the average network fee briefly dropped to about 1 sat/vB, and the mempool was nearly empty. But this isn't the norm. Just a few weeks earlier, inscription activity related to the Rune protocol generated over 600,000 transactions per day, accounting for about 25% of total network fees, directly pushing daily transaction volume above 820,000. When congestion hits, fees can jump dozens of times from 1 sat/vB in an instant.
Prerequisites
A pending transaction not yet broadcast, and you know the amount of BTC you want to send and the number of UTXOs in your wallet (the more UTXOs, the larger the transaction size, and the higher the total fee for the same rate).
An internet connection to access mempool monitoring tools (such as mempool.space).
The wallet supports RBF (Replace-By-Fee). Most mainstream wallets have it enabled by default. If you're unsure, check for an "Enable RBF" option in wallet settings before sending.
Step 1: Check the Current Mempool and Congestion Level
First, open mempool.space and take a look at the recommended fee tiers (high, medium, low) in the upper right corner, as well as the total backlog of transactions in the mempool. You don't need to go deep; just note two numbers: the current "minimum effective fee rate" in sat/vB, and whether this number has been rising or falling over the past hour.
How to:
High priority (next block): usually represents the fee rate for the fastest confirmation.
Medium priority (within 3 blocks): confirmation within approximately 30 minutes.
Low priority (6 blocks or more): confirmation within about 1 hour.
If the low-priority fee rate shown is similar to your wallet's default low fee rate, then sending now isn't a bad deal. If the low-tier fee has already surged above 50 sat/vB, it indicates congestion has begun.
Completion criteria: You have noted the current low, medium, and high sat/vB values.
Step 2: Decide Based on Urgency
With the current fee rates, consult this table:
| Your Situation | Decision |
|---|---|
| Not in a hurry, these coins are destined for cold storage/cross-chain bridge anyway | Wait. Check again during off-peak hours (weekends, weekday evenings); fees are usually lower. |
| The market is volatile, you urgently need to sell or buy the dip | Send now. Choose "medium priority" or "high priority". Don't gamble on fees to save a few dollars. |
| Large transaction amount but time-insensitive | Wait. You can schedule the send for late night UTC or over the weekend; fees could drop 30%–50%. |
Completion criteria: You've identified which category you fall into and have decided to send or wait.
Step 3: If You Send — Set the Fee Manually, Don't Use Wallet Default
If you decide to send now, don't just click the wallet's "quick" button. Go to mempool.space and check the "current minimum confirmable fee rate" (i.e., fee floor), then add 5–10 sat/vB to it.
How to: On the wallet's send page, enter your checked fee rate in the "custom fee" field. If you're using the OneKey wallet, its confirmation page already offers three speed presets (Fast/Medium/Slow); you can directly refer to its recommendations based on real-time on-chain fees.
Completion criteria: After broadcasting the transaction, enter your TXID on mempool.space. The status should show "Pending", and the fee rate should be ranked near the top of the mempool.
Step 4: If You Wait — Set Reminders, Don't Just Wait Idly
If you decide to wait, don't just wait indefinitely. What you need to do: Wait until the mempool clears before sending.
How to: mempool.space offers a "mempool clearance estimate" feature that shows how many blocks are needed to clear the current backlog. Normally, most low-fee transactions can be cleared within about an hour. If the mempool size exceeds 300 MB (the Bitcoin Core default limit), low-fee transactions may even be evicted by nodes and returned to your wallet.
Common failure reason: Many people browse social media while waiting, and as soon as they see someone say "BTC network fees crashed," they immediately send a transaction, without realizing that "crash" might be data from several minutes ago. The mempool changes by the second; by the time you see the info, fees may have already been pushed up by a new wave of inscription activity. The correct approach is to watch the real-time charts on mempool.space, not someone else's screenshots or posts.
Risk Warning
If you have broadcast a transaction but it remains unconfirmed, and the wallet does not have RBF enabled, you cannot accelerate it by "bumping the fee" via replacement. You can only wait it out or use the "child-pays-for-parent" (CPFP) method — which requires another unspent UTXO to pay a higher fee. Therefore, before sending, make sure the wallet's RBF toggle is on. Additionally, exchange withdrawals use batch transactions; you don't control the fee rate—the exchange sets it uniformly. During peak times, they may proactively increase miner fees to ensure timely delivery, so your personal decision to send or wait matters less.
Verification After Completing the Operation
If you sent: Enter your TXID on mempool.space, see the status change from "Pending" to "Confirmed", and note the block height of the transaction.
If you waited: Log in to mempool.space, and when the "current low-priority fee rate" drops to the 1–5 sat/vB range and the total mempool backlog is below 100 MB, you can prepare to send. Next check: 2 hours later.
