Transaction

f4eef797e022f07b50f2a463362135124a9b2400a04077bca7c07b772b372245
Timestamp (utc)
2024-03-22 09:44:55
Fee Paid
0.00000013 BSV
(
0.00901082 BSV
-
0.00901069 BSV
)
Fee Rate
10.31 sat/KB
Version
1
Confirmations
93,839
Size Stats
1,260 B

2 Outputs

Total Output:
0.00901069 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMð<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=760.msg8410#msg8410">Quote from: davidonpda on August 09, 2010, 08:07:26 PM</a></div><div class="quote">The problem with the time stamps, is a unix time stamp as a 32 bit integer WILL overflow in 2038. I am a programmer, but you can find more info on it by googling unix time problem or 2038 <img alt="Smiley" border="0" src="/static/img/emoticons/smiley.gif"/><br/></div><br/>I understand the Y2038 problem from a layman's perspective.&nbsp; My point was that, I doubted that a Y2038 problem exists within the structure of bitcoin.&nbsp; Since the timestamp is relative only to a particular position within the blockchain, there is no reason that a client should require an accurate timestamp within the block.&nbsp; And then, what would that be?&nbsp; GMT?&nbsp; I'm pretty sure that my client is doing fine with local time.&nbsp; If that could be getting any successful blocks rejected, let me know, please.</div> text/html
    https://whatsonchain.com/tx/f4eef797e022f07b50f2a463362135124a9b2400a04077bca7c07b772b372245