Bitcoin mined an empty block at height 954,352, according to Mempool data.
Summary
- SpiderPool mined Bitcoin block 954,352 with only the coinbase transaction and no user transactions included.
- The 62-second gap points to fast miner template timing, not a clear network problem today.
- Empty Bitcoin blocks have happened before, but repeated cases would draw closer miner behavior scrutiny.
The block contained only the coinbase transaction, meaning it carried the miner reward but no regular user transactions.
The block was mined by SpiderPool. Mempool data showed a timestamp of 2026-06-19 04:27 and a block weight of 1.16 kWU.
Short block gap draws attention
The empty block came about 62 seconds after the previous Bitcoin block. That short gap is the main reason traders and network watchers flagged the event.
A fast block gap can leave miners working with a coinbase-only template before a fuller transaction template reaches mining hardware. That can produce a valid empty block.
Meanwhile, empty Bitcoin blocks are not new. In June 2024, Mempool Research noted that empty blocks have appeared throughout Bitcoin’s history, though they are now rare.
The research explains that mining pools may send empty templates because they are smaller and faster to transmit. The tradeoff is that the miner gives up transaction fees from that block.
Repeated behavior would matter more
A single empty block does not show a Bitcoin network issue. It does not halt settlement, reverse transactions, or break consensus rules.
The event would matter more if empty blocks appeared repeatedly. That could raise fresh questions about miner timing choices and whether some pools are prioritizing speed over fee revenue.
As previously reported by crypto.news, miner timing incentives have been discussed in research around selfish mining risks. This empty Bitcoin block is not the same as selfish mining, but it adds another data point for analysts watching miner behavior.
Moreover, as crypto.news covered in 2022, Bitcoin SV faced empty-block issues, though that case involved a different network and a more severe pattern. For Bitcoin, block 954,352 is best read as a rare but known mining event unless the pattern continues.
