Transaction

772e9d0a97ecf54e70b0bc7b0a43b1c0b9d0000ef4f2e0df34b2f575044eda40
2024-03-22 01:10:52
0.00000018 BSV
(
0.00226236 BSV
-
0.00226218 BSV
)
10.42 sat/KB
1
70,869
1,726 B

2 Outputs

Total Output:
0.00226218 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÂ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=383.msg3295#msg3295">Quote from: satoshi on July 15, 2010, 09:40:34 PM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=383.msg3269#msg3269">Quote from: knightmb on July 15, 2010, 07:37:10 PM</a></div><div class="quote">On Windows, the priority of the Coin Generation is still net for normal. If you run BitCoin in Generate Coin mode, then load up something to eat up all the CPU (like CPU hog for example: <a href="http://www.microtask.ca/cpuhog.html">http://www.microtask.ca/cpuhog.html</a>) you'll see that both BitCoin and CPU hog share the CPU 50/50 instead of CPU Hog taking all the CPU and BitCoin running only on idle/low process. The khash/s is also reduced in half, so further evidence that the threads are not running in a lower than normal prioirty.<br/></div>I was not able to reproduce this.&nbsp; I have dual-proc, so I ran two memory hogs.&nbsp; Bitcoin got 0% of CPU according to the task manager.&nbsp; The khash/sec meter stayed stuck because it couldn't get any CPU to update it.<br/><br/>Do you have dual-proc?&nbsp; Are you sure you weren't running a single processor hog?<br/></div>LOL, I think you are right. I've got waaaayy too many PCs around me and it's difficult to keep track of which is single core, dual core, quad, 8 core, etc. I'll test it again on the single proc PC and see what happens.</div> text/html
    https://whatsonchain.com/tx/772e9d0a97ecf54e70b0bc7b0a43b1c0b9d0000ef4f2e0df34b2f575044eda40