Transaction

ef9d9cf960bf42e778778a351bbbee80bc197c40b97d7bf791668bc8e667fb98
Timestamp (utc)
2024-03-26 16:19:25
Fee Paid
0.00000012 BSV
(
0.00942719 BSV
-
0.00942707 BSV
)
Fee Rate
10.3 sat/KB
Version
1
Confirmations
93,230
Size Stats
1,165 B

2 Outputs

Total Output:
0.00942707 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post">Thanks for the object!<br/><br/>There are two things I noticed:<br/>1) The Intel object runs at 3269khash/s on my AMD64 (vs. 3778khash/s) so it's less optimized than the AMD64 code.<br/><br/>2) AMD64 moves less data around and does more calculations. Sometimes it even abuses floating point instructions for integers.<br/><br/>Could you drop in my sha256.o from <a href="http://ul.to/2ckndx">http://ul.to/2ckndx</a> to cryptopp/obj/, delete test (not the .cpp!!) and recompile test using make -f makefile.unix test (take care it doesn't recompile sha256.cpp to sha256.o). Then run test again. It should be using AMD64 code now. Maybe it works better...<br/><br/>If not we've found that AMD64 is about four times faster than Intel at SSE2 integer vector arithmetic. Anyone working on a floating point SHA256 implementation? <img alt="Wink" border="0" src="/static/img/emoticons/wink.gif"/></div> text/html
    https://whatsonchain.com/tx/ef9d9cf960bf42e778778a351bbbee80bc197c40b97d7bf791668bc8e667fb98