<blockquote>
  <p>Is it because they're mining too fast for the timestamp to change?</p>
</blockquote>

<p>Precisely - even a relatively slow CPU can hash several hundred headers every second. Modern day ASICs can hit 100+ terahashes per second - ripping through the entire nonce space several times over.</p>

<p>Moreover, the timestamp is also a 4 byte value - miners do use it, in conjunction with the nonce, merkle root, and block version to create a much larger search space. Even so, the majority of combinations of all of these do not result in valid blocks.</p>

CC BY-SA 4.0
2020-04-12T13:50:46.950Z
2020-04-12T13:50:46.950Z
Raghav Sood
<p>As the title says.</p>

<p>If the timestamp is constantly changing with every guess, why does the miner also include the nonce? Is it because they're mining too fast for the timestamp to change?</p>

<mining-theory><hash><nonce>
Why do miners need a nonce if the timestamp changes the hash of the block?
user95756
# Why do miners need a nonce if the timestamp changes the hash of the block?

(Asked by: username_0 on 2020-04-12)

As the title says.

If the timestamp is constantly changing with every guess, why does the miner also include the nonce? Is it because they're mining too fast for the timestamp to change?

**Tags:** mining-theory, hash, nonce


---

## 1 answers

### Answer by username_1 on 2020-04-12. Score: 3 | Accepted answer

> Is it because they're mining too fast for the timestamp to change?

Precisely - even a relatively slow CPU can hash several hundred headers every second. Modern day ASICs can hit 100+ terahashes per second - ripping through the entire nonce space several times over.

Moreover, the timestamp is also a 4 byte value - miners do use it, in conjunction with the nonce, merkle root, and block version to create a much larger search space. Even so, the majority of combinations of all of these do not result in valid blocks.


---

