Transaction

793b360b0bb14b5fb2b9e4064a1d1a5c5e2cd7c56e6a5b4fd4b328c69cd5404a
Timestamp (utc)
2024-03-28 08:24:10
Fee Paid
0.00000013 BSV
(
0.00601493 BSV
-
0.00601480 BSV
)
Fee Rate
10.66 sat/KB
Version
1
Confirmations
93,084
Size Stats
1,219 B

2 Outputs

Total Output:
0.00601480 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/793b360b0bb14b5fb2b9e4064a1d1a5c5e2cd7c56e6a5b4fd4b328c69cd5404a