Transaction

79ac2d4e050af7330ff55e9fad286e46971fa1a1cb89cb46971426368c01acff
Timestamp (utc)
2024-03-22 15:44:49
Fee Paid
0.00000013 BSV
(
0.00486345 BSV
-
0.00486332 BSV
)
Fee Rate
10.66 sat/KB
Version
1
Confirmations
94,068
Size Stats
1,219 B

2 Outputs

Total Output:
0.00486332 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÇ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=753.msg8233#msg8233">Quote from: lfm on August 08, 2010, 01:13:30 PM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=753.msg8230#msg8230">Quote from: tcatm on August 08, 2010, 11:56:54 AM</a></div><div class="quote">Did you compile it yourself? There's a define in makefile.unix. Something like -DCRYPTOPP_DISABLE_SSE2. Remove that. Else the SHA256_Transform will return the initstate. I had the same problem when switchting to 0.3.6.<br/></div><br/>That seems to be the root of the problem. I think even the bundled binary for Linux 64 in 0.3.8 was compiled wrong then.<br/></div><br/>I just tested it out, I get the same results. Repeating values with stock, more random values with the flag modification. Probably needs to be fixed for the next release, though I'm not sure how mine are generating anything then?</div> text/html
    https://whatsonchain.com/tx/79ac2d4e050af7330ff55e9fad286e46971fa1a1cb89cb46971426368c01acff