Checking on
mempool it looks like block
https://mempool.
spaceblock/00000000000000000001b6e6909ce860dd325605dd95c1f7e7743a98714358d1909310 was completed after
909311 despite being the earlier block. This suggests that the earlier block was delayed for some reason and the later one ended up getting confirmed firsts.
Your first link has an error.
The block timestamps are not authoritative, miners can include timestamp partially to their liking as long they adhere to the rules. The rules say that timestamps need to be:
- Median Past Time (MPT), new block's timestamp must be later than the median time of the last 11 mined blocks.
- A timestamp must not be more than 2 hours in the future.
Source:
https://blog.bitmex.com/bitcoins-block-timestamp-protection-rules/. When you want to know which block is confirmed first, you need to look at the block number and hashes not at the timestamp.
For this kind of question it is important to remember how Bitcoin works. Every new block has the hash of the previous block in its header. You just need a tool to analyze and compare the two block headers and you will know the answer to your question. In the case of mempool.space, you have these nice arrows that work as an alternative to the prevhash field. So when you click on "previous" or "next" it tells you the right order of the block, regardless of the timestamps.
On other explorers you can see this field explicitly:
I think I have given a pretty complete answer, please let me know if these are any other questions.
