<p>the timestamp is very important to authenticate when the block was created and also it has various functions to mempool and the nonce .
just for little deep knowledge of time stamp :-
1- the timestamp refreshes every 1 second and in that 1 second the nonce should be able to find the golden nonce which is approx around 0-4 Billion iterations within the sec. which seems impossible .</p>

<p>2- it's impossible but it can be possible for the people minning together they can use their combined computational power to solve the 0-4 billion iterations within less than second which then the hash could be gained and the block is given to them with fee associated to it </p>

<p>and lastly the nonce do changes every time when the timestamp changes within 1 second</p>

CC BY-SA 4.0
2019-12-16T09:57:57.290Z
2019-12-16T09:57:57.290Z
howdyAnkit
<p>The timestamp exists so there will be a permanent record of when the block was found. The timestamp needs to pass some sanity tests for the block to be considered valid.</p>

<p>One of the key uses of the timestamp is in calculating difficulty retargets.</p>

CC BY-SA 3.0
2013-08-27T13:23:00.617Z
But the timestamp (block header field) is hashed? How is that useful to the blockchain? Surely the time the new block is announced to the blockchain is the time value that is recorded?
Anonymous
CC BY-SA 3.0
2013-08-27T13:27:00.260Z
@Anonymous: The network isn't a monolithic entity. Different nodes get the block at different times, and new nodes don't have firsthand knowledge of the history. Having the timestamp part of the hashed data means everyone can agree on the timestamp, and this can never be changed without altering the hash and breaking the chain. The synchronization challenge is why the blockchain exists in the first place.
Meni Rosenfeld
CC BY-SA 3.0
2013-09-06T16:13:56.990Z
Does the time stamp change every few seconds. If yes then if a miner is still hashing while time stamp changes and then it finds a hash lower that target, will that hash be considered valid if other conditions are satisfied?
bytefire
CC BY-SA 3.0
2013-09-07T17:05:26.277Z
@bytefire: The miner chooses which timestamp to put in the block. Nodes will reject blocks with timestamp that doesn't make sense, but that's on a scale of hours, so there shouldn't be a problem. (See also http://bitcoin.stackexchange.com/questions/3743/how-can-an-earlier-block-have-a-later-timestamp).
Meni Rosenfeld
CC BY-SA 3.0
2013-08-27T13:21:36.477Z
2013-08-27T13:21:36.477Z
Meni Rosenfeld
<p>What is the reason for the timestamp field in the block header? Surely the nonce should be the only property that changes? Should the nonce reset to 0 everytime the timestamp changes?</p>

<blockchain><mining-theory><timestamp><block-header>
Why the timestamp component of the block header?
Anonymous
# Why the timestamp component of the block header?

(Asked by: username_0 on 2013-08-27)

What is the reason for the timestamp field in the block header? Surely the nonce should be the only property that changes? Should the nonce reset to 0 everytime the timestamp changes?

**Tags:** blockchain, mining-theory, timestamp, block-header


---

## 2 answers

### Answer by username_2 on 2013-08-27. Score: 9 | Accepted answer

The timestamp exists so there will be a permanent record of when the block was found. The timestamp needs to pass some sanity tests for the block to be considered valid.

One of the key uses of the timestamp is in calculating difficulty retargets.

> **Comments:**
> **username_0**: But the timestamp (block header field) is hashed? How is that useful to the blockchain? Surely the time the new block is announced to the blockchain is the time value that is recorded?  
> **username_2**: @username_0: The network isn't a monolithic entity. Different nodes get the block at different times, and new nodes don't have firsthand knowledge of the history. Having the timestamp part of the hashed data means everyone can agree on the timestamp, and this can never be changed without altering the hash and breaking the chain. The synchronization challenge is why the blockchain exists in the first place.  
> **username_3**: Does the time stamp change every few seconds. If yes then if a miner is still hashing while time stamp changes and then it finds a hash lower that target, will that hash be considered valid if other conditions are satisfied?  
> **username_2**: @username_3: The miner chooses which timestamp to put in the block. Nodes will reject blocks with timestamp that doesn't make sense, but that's on a scale of hours, so there shouldn't be a problem. (See also http://bitcoin.stackexchange.com/questions/3743/how-can-an-earlier-block-have-a-later-timestamp).  

---

### Answer by username_1 on 2019-12-16. Score: -1

the timestamp is very important to authenticate when the block was created and also it has various functions to mempool and the nonce .
just for little deep knowledge of time stamp :-
1- the timestamp refreshes every 1 second and in that 1 second the nonce should be able to find the golden nonce which is approx around 0-4 Billion iterations within the sec. which seems impossible .

2- it's impossible but it can be possible for the people minning together they can use their combined computational power to solve the 0-4 billion iterations within less than second which then the hash could be gained and the block is given to them with fee associated to it

and lastly the nonce do changes every time when the timestamp changes within 1 second


---

