Transaction

7b604896dbb444ee82195f7ead3a4877b2bc213a334eccf01ac4e9728531991f
Timestamp (utc)
2024-03-22 01:10:52
Fee Paid
0.00000009 BSV
(
0.00238184 BSV
-
0.00238175 BSV
)
Fee Rate
10.75 sat/KB
Version
1
Confirmations
94,179
Size Stats
837 B

2 Outputs

Total Output:
0.00238175 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMI<div class="post">As far as I can read C++, Bitcoin implementation stores timestamps as unsigned integers<br/>and block timestamp is a part of binary block format, of which a hash is computed.<br/>Since blocks are chained and the previous block is referenced in the current by it's hash,<br/>you cannot simply recompile the client with 64bit timestamps.<br/>You will need to recompute the whole chain, is that an option?<br/>Or we need to propose some transition plan to another binary block format.<br/><br/>Or, I am wrong and everybody should relax.<br/><br/>What do you think?</div> text/html
    https://whatsonchain.com/tx/7b604896dbb444ee82195f7ead3a4877b2bc213a334eccf01ac4e9728531991f