<p>It is neither of those, although it is closer to the first. The second makes no sense. A block is not validated once at a specific time, it is validated thousands of times at thousands of different places. No one cares at what time someone else validated a block, because everyone must validate the block for themselves.</p>
<p>It is a number chosen by the miner. They can choose any value that is likely to be accepted by other nodes at the time those other nodes first receive the new block. The rule is:</p>
<blockquote>
<p>A timestamp is accepted as valid if it is greater than the median timestamp of previous 11 blocks, and less than the network-adjusted time + 2 hours. &quot;Network-adjusted time&quot; is the median of the timestamps returned by all nodes connected to you.</p>
</blockquote>
<p>Since it is part of the block header that is included in the data hashed, it cannot be altered.</p>
<p>As it has one second resolution there are probably of the order of ten thousand values that other nodes would accept.</p>
<p>See <a href="https://bitcoin.stackexchange.com/q/12564/13866">Can a miner set the EXACT timestamp of a block?</a></p>

CC BY-SA 4.0
2022-04-09T13:00:05.627Z
2022-04-09T13:11:29.880Z
2022-04-09T13:11:29.880Z
RedGrittyBrick
<ol>
<li><p>The time block header was constructed</p>
</li>
<li><p>The time when block was validated?</p>
</li>
</ol>
<p>if 2, this means not only nonce is incremented +1 every time we have hashed block header but also timestamp increments and once we mine it and others validate, it stays to final the value? (the one which we see in the block header)</p>

<block><timestamp>
Which time does timestamp given in the block explorer represents?
Tesla Solution
# Which time does timestamp given in the block explorer represents?

(Asked by: username_0 on 2022-04-08)

1. The time block header was constructed
2. The time when block was validated?

if 2, this means not only nonce is incremented +1 every time we have hashed block header but also timestamp increments and once we mine it and others validate, it stays to final the value? (the one which we see in the block header)

**Tags:** block, timestamp


---

## 1 answers

### Answer by username_1 on 2022-04-09. Score: 2

It is neither of those, although it is closer to the first. The second makes no sense. A block is not validated once at a specific time, it is validated thousands of times at thousands of different places. No one cares at what time someone else validated a block, because everyone must validate the block for themselves.

It is a number chosen by the miner. They can choose any value that is likely to be accepted by other nodes at the time those other nodes first receive the new block. The rule is:

> A timestamp is accepted as valid if it is greater than the median timestamp of previous 11 blocks, and less than the network-adjusted time + 2 hours. "Network-adjusted time" is the median of the timestamps returned by all nodes connected to you.

Since it is part of the block header that is included in the data hashed, it cannot be altered.

As it has one second resolution there are probably of the order of ten thousand values that other nodes would accept.

See [Can a miner set the EXACT timestamp of a block?](https://bitcoin.stackexchange.com/q/12564/13866)


---

