<p>The timestamps on those blocks are indeed quite varied so I think that blockr.io is not using the timestamp field in the block as sole timing information, instead using something like <code>min(relayed time, block timestamp)</code> so that blocks that have a future timestamp are shown as "right now" because they use the relayed time. They probably are not only using the relayed time since in that case they'd be misdating all blocks after downtime.</p>

<p>TL;DR: do not trust the timestamp field in the block, it can be manipulated.</p>

CC BY-SA 3.0
2016-04-11T13:07:49.060Z
the question is more why there are future timestamps in test net ? Are you sure that even main net does not check the block time ?
Pavel Niedoba
CC BY-SA 3.0
2016-04-11T13:48:28.017Z
Yes, it is not possible to synchronize clocks in a distributed system, so Bitcoin limits the checking to a rather large range of [-2 hours:+2 hours], which is what you're observing. From an observer the cases of the block creator putting a timestamp in the future and the observer's clock lagging is indistinguishable.
cdecker
CC BY-SA 3.0
2016-04-10T16:43:24.023Z
2016-04-10T16:43:24.023Z
cdecker
<p>I can see <a href="http://tbtc.blockr.io/" rel="nofollow noreferrer">http://tbtc.blockr.io/</a> time of block are showing "right now". When I click "all blocks" the time is two hours ahead of "now". I don't think it's blockr time zone problem, because </p>

<p>1) when I submit transaction, it will show correct time</p>

<p>2) my bitcoinj wallet also showing future time against </p>

<pre><code>System.currentTimeMillis();
</code></pre>

<p>which is UTC time. (I use ntp and it happens on two different computers)</p>

<p>Anybody have an idea why this is happening? </p>

<p><a href="https://i.sstatic.net/pNrVQ.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/pNrVQ.png" alt="enter image description here"></a></p>

CC BY-SA 3.0
2016-04-03T23:21:00.997Z
It might be that any times in the future get converted to right now. It might be good to put a screenshot, though, so that you can still see the issue even if the problem gets fixed.
morsecoder
CC BY-SA 3.0
2016-04-04T09:30:44.090Z
well the screenshot shows last 11 blocks, considering they go faster in testnet, the last one should be half hour old
Pavel Niedoba
<testnet>
test net block time wrong
Pavel Niedoba
# test net block time wrong

(Asked by: username_0 on 2016-04-03)

I can see <http://tbtc.blockr.io/> time of block are showing "right now". When I click "all blocks" the time is two hours ahead of "now". I don't think it's blockr time zone problem, because

1) when I submit transaction, it will show correct time

2) my bitcoinj wallet also showing future time against

```
System.currentTimeMillis();

```

which is UTC time. (I use ntp and it happens on two different computers)

Anybody have an idea why this is happening?

[![enter image description here](https://i.sstatic.net/pNrVQ.png)](https://i.sstatic.net/pNrVQ.png)

**Tags:** testnet

> **Comments:**
> **username_1**: It might be that any times in the future get converted to right now. It might be good to put a screenshot, though, so that you can still see the issue even if the problem gets fixed.  
> **username_0**: well the screenshot shows last 11 blocks, considering they go faster in testnet, the last one should be half hour old  

---

## 1 answers

### Answer by username_2 on 2016-04-10. Score: 1

The timestamps on those blocks are indeed quite varied so I think that blockr.io is not using the timestamp field in the block as sole timing information, instead using something like `min(relayed time, block timestamp)` so that blocks that have a future timestamp are shown as "right now" because they use the relayed time. They probably are not only using the relayed time since in that case they'd be misdating all blocks after downtime.

TL;DR: do not trust the timestamp field in the block, it can be manipulated.

> **Comments:**
> **username_0**: the question is more why there are future timestamps in test net ? Are you sure that even main net does not check the block time ?  
> **username_2**: Yes, it is not possible to synchronize clocks in a distributed system, so Bitcoin limits the checking to a rather large range of [-2 hours:+2 hours], which is what you're observing. From an observer the cases of the block creator putting a timestamp in the future and the observer's clock lagging is indistinguishable.  

---

