# Strange block time on block 330560

**URL:** <https://forum.safex.org/t/strange-block-time-on-block-330560/6829>\
**Category:** General Discussion\
**Created:** [January 8, 2020, 8:29pm UTC](https://forum.safex.org/t/strange-block-time-on-block-330560/6829 "2020-01-08T20:29:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mark0spasic](https://forum.safex.org/user_avatar/forum.safex.org/mark0spasic/32/2653_2.png) [@mark0spasic](https://forum.safex.org/u/mark0spasic)\
**Post date:** [January 8, 2020, 8:29pm UTC](https://forum.safex.org/t/strange-block-time-on-block-330560/6829/1 "2020-01-08T20:29:39Z")

</div>

Can anyone explane strange blocktine on block number 330560? As you can see on picture block 330560 is younger in time then next block and it should be older. Maybe devs can explain.

 ![Untitled](https://forum.safex.org/uploads/default/original/2X/7/7313093f43793fb591d3f39e9854ebe19603aced.jpeg)

---

<div class="post-metadata">

**Author:** ![dandabek](https://forum.safex.org/user_avatar/forum.safex.org/dandabek/32/268_2.png) [@dandabek](https://forum.safex.org/u/dandabek)\
**Post date:** [January 8, 2020, 11:57pm UTC](https://forum.safex.org/t/strange-block-time-on-block-330560/6829/2 "2020-01-08T23:57:15Z")

</div>

> [@mark0spasic](#):
>
> 330560

Checked that, yes indeed that did happen: it is because the miners can set their own timestamp. .So if someone who mined that block had a misconfigured system time, it would apply to the block.

Timestamps are only partially used in the block production so they are not totally essential to be accurate. Block height is linear incremental, and the timestamps ought to be ball park within a range.

Sorry, A better explanation is due here. To describe exactly how the algorithm is utilizing timestamps. Though just to rest assured that it is not dangerous here and there to be a few minutes off.