Mempool Onaysız İşlem Sayısı

The mempool transaction count: transactions broadcast and validated but not yet mined into a block. It complements the mempool size (bytes) chart — the data source's own framing: bytes estimate how long congestion will last, counts show how many transactions are causing it. Same aggregation across blockchain.com's node cluster, log axis.

The two charts usually move together; divergences are worth a closer look. Counts surging while bytes stay mild means a flood of tiny transactions — the 2023 BRC-20/inscription minting waves were the textbook case, pushing pending counts into the hundreds of thousands with minimal individual size. Bytes rising on flat counts means bulky transactions — typically UTXO consolidation sweeps, which miners and exchanges deliberately schedule for cheap-fee windows.

The mempool is not first-come-first-served: miners fill blocks from the highest feerate (sats/vByte) down, and low bids wait indefinitely. A stuck transaction meets one of three fates: confirmation once fee conditions ease; eviction (nodes drop the lowest-feerate transactions when the mempool is full) or expiry (14-day default); or a sender-initiated RBF fee bump. A falling count therefore doesn't always mean the backlog cleared — it may mean low-fee transactions were purged en masse.

Three caveats. Every node sees a different queue; this is an aggregated approximation. Counts ignore economic weight — an inscription mint and a 10,000 BTC transfer each count as one. And there is no stable causal link to price: treat this as a real-time thermometer of on-chain demand and fee pressure. Sustained high counts mean on-chain transfers are slow and expensive — which genuinely degrades exchange deposit and withdrawal experience.

Beyond network data, see the broader market via total crypto market cap and BTC liquidations.