<p>When your bitcoin node connects to another node it requests the current timestamp from the node.  It stores this value to calculate the offset from your PC's clock.  As you may be aware the bitcoin network calculates the network time based upon the average offset of the peers that it is connected to.  This will never alter the systems clock more than 70 minutes in regards to network time calculations.</p>

<p>References:
<a href="https://en.bitcoin.it/wiki/Block_timestamp" rel="nofollow">Block timestamp</a> </p>

CC BY-SA 3.0
2016-01-15T03:33:44.190Z
2016-01-15T03:33:44.190Z
Mark S.
<p>As in, not the miner's timestamp in the blockheader which can be +/- 2 hours, but the receiving node's local time. My concern is the real-world time that elapses between blocks.</p>

<json-rpc><nodes><timestamp>
Is there a way to get the node's local time when a block was received?
pinhead
# Is there a way to get the node's local time when a block was received?

(Asked by: username_0 on 2016-01-14)

As in, not the miner's timestamp in the blockheader which can be +/- 2 hours, but the receiving node's local time. My concern is the real-world time that elapses between blocks.

**Tags:** json-rpc, nodes, timestamp


---

## 1 answers

### Answer by username_1 on 2016-01-15. Score: 1

When your bitcoin node connects to another node it requests the current timestamp from the node. It stores this value to calculate the offset from your PC's clock. As you may be aware the bitcoin network calculates the network time based upon the average offset of the peers that it is connected to. This will never alter the systems clock more than 70 minutes in regards to network time calculations.

References:
[Block timestamp](https://en.bitcoin.it/wiki/Block_timestamp)


---

