user127674: I am just learning mining process.
Today I learned that we have to find nonce for given block header.
And for block header we need timestamp in UTC
I took the timestamp data from below link of 125552 block
https://www.blockchain.com/btc/block/00000000000000001e8d6829a8a21adc5d38d0a473b144b6765798e61f98bd1d
And used the below linke to convert it from UTC to seconds
https://www.epochconverter.com/
And I am getting 1305998760
But according to the example in the below link its 1305998791
https://en.bitcoin.it/wiki/Block_hashing_algorithm
And what is endian in the above link
Can anyone please help me what am I missing
Thanks in advance

user13866: Displayed precision ≠ Stored precision
Note that the block timestamp is stored as a 4-byte number of seconds since 1970-01-01T00:00 UTC (the Unix epoch). However Blockchain.com show this in a more human readable form rounded or truncated to the nearest minute (2011-05-21 18:26). So if you convert that human readable time back to an integer, you will get a value that is different by a number of seconds between 0 and 59
Endianness
See Wikipedia article on endianness. There are two possible orderings of the bytes of a multi-byte integer. You can start with least significant byte (LSB) or with most significant byte (MSB). Internet standard "Network Order" is big-endian. X86 architecture computers use little-endian byte-order. Some other hardware architectures use big-endian byte-order.
Bitcoin
Bitcoin mostly uses little endian. Even for data transmitted over the Internet. See documentation for block hashing. Note that it talks about the use of big-endian for hexadecimal display of values and little-endian for storage.
Timestamps are not accurate
See Why don't the timestamps in the block chain always increase?

A timestamp is accepted as valid if it is greater than the median timestamp of previous 11 blocks, and less than the network-adjusted time + 2 hours. "Network-adjusted time" is the median of the timestamps returned by all nodes connected to you.

So don't be surprised if later blocks sometimes have earlier timestamps. Children can be older than their parents.

127674: <p>I am just learning mining process.
Today I learned that we have to find nonce for given block header.</p>
<p>And for block header we need timestamp in UTC</p>
<p>I took the timestamp data from below link of 125552 block
<a href="https://www.blockchain.com/btc/block/00000000000000001e8d6829a8a21adc5d38d0a473b144b6765798e61f98bd1d" rel="nofollow noreferrer">https://www.blockchain.com/btc/block/00000000000000001e8d6829a8a21adc5d38d0a473b144b6765798e61f98bd1d</a></p>
<p>And used the below linke to convert it from UTC to seconds
<a href="https://www.epochconverter.com/" rel="nofollow noreferrer">https://www.epochconverter.com/</a></p>
<p>And I am getting 1305998760</p>
<p>But according to the example in the below link its 1305998791
<a href="https://en.bitcoin.it/wiki/Block_hashing_algorithm" rel="nofollow noreferrer">https://en.bitcoin.it/wiki/Block_hashing_algorithm</a></p>
<p>And what is endian in the above link</p>
<p>Can anyone please help me what am I missing</p>
<p>Thanks in advance</p>
 13866: <h2>Displayed precision ≠ Stored precision</h2>
<p>Note that the block timestamp is stored as a 4-byte number of <strong>seconds</strong> since 1970-01-01T00:00 UTC (the Unix epoch). However Blockchain.com show this in a more human readable form rounded or truncated to the nearest <strong>minute</strong> (2011-05-21 18:26). So if you convert that human readable time back to an integer, you will get a value that is different by a number of seconds between 0 and 59</p>
<h2>Endianness</h2>
<p>See Wikipedia article on <a href="https://en.wikipedia.org/wiki/Endianness" rel="nofollow noreferrer">endianness</a>. There are two possible orderings of the bytes of a multi-byte integer. You can start with least significant byte (LSB) or with most significant byte (MSB). Internet standard &quot;Network Order&quot; is big-endian. X86 architecture computers use little-endian byte-order. Some other hardware architectures use big-endian byte-order.</p>
<h2>Bitcoin</h2>
<p>Bitcoin mostly uses little endian. Even for data transmitted over the Internet. See <a href="https://en.bitcoin.it/wiki/Block_hashing_algorithm" rel="nofollow noreferrer">documentation for block hashing</a>. Note that it talks about the use of big-endian for hexadecimal display of values and little-endian for storage.</p>
<h2>Timestamps are not accurate</h2>
<p>See <a href="https://bitcoin.stackexchange.com/q/915/13866">Why don&#39;t the timestamps in the block chain always increase?</a></p>
<blockquote>
<p>A timestamp is accepted as valid if it is greater than the median timestamp of previous 11 blocks, and less than the network-adjusted time + 2 hours. &quot;Network-adjusted time&quot; is the median of the timestamps returned by all nodes connected to you.</p>
</blockquote>
<p>So don't be surprised if later blocks sometimes have earlier timestamps. Children can be older than their parents.</p>
