Mempool Transaction Count by Fee Rate Tier
- 1M1M
- 3M3M
- 6M6M
- 1Y1Y
- ALLALL
- ValueValue
- ShareShare
About this metric
What it measures
Mempool Transaction Count by Fee Rate Tier counts unconfirmed transactions in nine fee-rate bands, measured in transactions. The labels 0–1, 1–2, 2–3, 3–4, 4–5, 5–7, 7–10, 10–50 and 50+ sat/vB refer to the fees offered per virtual byte, not BTC transferred.
How to read it
A queue concentrated in low-rate bands differs from one with many higher-rate transactions competing for inclusion. Track which bands are growing rather than the total alone: the 5–7 sat/vB band reached 198,551 transactions on August 29, 2023, while the 50+ sat/vB band peaked on a different date, December 31, 2023.
Every transaction counts once regardless of its size or number of recipients. A large count of small transactions can require less block space than fewer bulky ones, so use the size breakdown alongside it. Node relay policies and the timing of daily observations also affect the queue recorded.
- Frequency
- Daily (UTC 00:00)
- Asset
- BTC
- Category
- Mempool
- Type
- Breakdown
- Data since
- 2021-10-15
- Latest data
- 2026-10-27
FAQ
Does each pending transaction represent one payment?
No. A transaction can pay several recipients, move funds between the sender’s wallets or consolidate inputs. Transaction count is therefore neither payment count nor user count.
Why can lower-fee bands grow while higher-fee bands shrink?
Blocks can clear higher-rate transactions while lower-rate ones remain waiting or keep arriving. Replacements can also change the mix, so the chart follows the queue’s composition rather than a fixed set of transactions.
Can these counts tell me how many blocks I must wait?
Counts alone cannot do that because transaction sizes differ and new bids keep arriving. The virtual-byte distribution is more relevant to block-space demand, but even that cannot guarantee a confirmation deadline.
