Transaction

d482aa622852257a734a9da7543d3fe50646a2ef84b4a361f0d59dfd791483da
Timestamp (utc)
2024-03-21 23:28:33
Fee Paid
0.00000013 BSV
(
0.00366658 BSV
-
0.00366645 BSV
)
Fee Rate
10.05 sat/KB
Version
1
Confirmations
95,523
Size Stats
1,293 B

2 Outputs

Total Output:
0.00366645 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=753.msg8306#msg8306">Quote from: ArtForz on August 09, 2010, 12:31:45 AM</a></div><div class="quote">Just had a "fun" gdb session with the official 0.3.8 linux 64 bit binary on debian sid.<br/>Same bug, output state on return from SHA256Transform always == initial state.<br/>So... did someone really generate a block running the official 0.3.8 64 bit linux binary (the one in bin/64)?<br/>Oh, and from a quick glance at the svn changelog, that bug probably has been there since r118 = 0.3.6.<br/>Oh, and who THE FUCK thought stripping the official binary was a good idea? I just wasted half an hour hunting down SHA256Transform in a disassembler.<br/><br/></div><br/>Not on 64bit linux, just 32bit and 64bit everything else in between (Linux/Windows)<br/><br/>I didn't notice until I checked the generation dates against the release dates of the software.<br/><br/>If you don't strip the debug symbols the binary is 8 times it's normal size.</div> text/html
    https://whatsonchain.com/tx/d482aa622852257a734a9da7543d3fe50646a2ef84b4a361f0d59dfd791483da