pull down to refresh

Mempool.space showing a block out of order (Time of block vs block number)
105 sats \ 5 comments \ @Wumbo 12 Apr bitcoin
https://m.stacker.news/26381
Block 838906 has a time of ‎2024-04-12 15:11:01 Block 838907 has a time of 2024-04-12 15:08:41
Tell me how I am stupid and what am I missing?
write
preview
related posts
20 sats \ 0 replies \ @kristapsk 12 Apr
It's likely timestamp miner put into block, not when block was received, can be off for hours.
reply
31 sats \ 0 replies \ @theinstagibbs 12 Apr
A block is allowed to have a timestamp strictly higher than the median of the last 11(?) blocks.
Timestamps are difficult in distributed systems.
reply
21 sats \ 0 replies \ @Murch 13 Apr
A block’s time stamp is valid when it's greater than the median of the last eleven blocks and less than the evaluating node’s current time plus two hours: https://bitcoin.stackexchange.com/q/915/5406
reply
1 sat \ 0 replies \ @nym 12 Apr
Timestamping is hard
reply
0 sats \ 0 replies \ @jp305 12 Apr
That's interesting.... from mempool's doc:
When a new block is found, mining pools send miners a block template with no transactions so they can start searching for the next block as soon as possible. They send a block template full of transactions right afterward, but a full block template is a bigger data transfer and takes slightly longer to reach miners.
In this intervening time, which is usually no more than 1-2 seconds, miners sometimes get lucky and find a new block using the empty block template.
reply