Transaction

d2dcc7d6839f6befc02e7f97cbbdb47dec33b4e18069c293145e05d786ec89fc
Timestamp (utc)
2024-03-22 19:09:08
Fee Paid
0.00000014 BSV
(
0.00249658 BSV
-
0.00249644 BSV
)
Fee Rate
10.56 sat/KB
Version
1
Confirmations
94,089
Size Stats
1,325 B

2 Outputs

Total Output:
0.00249644 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM0<div class="post"><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?</div> text/html
    https://whatsonchain.com/tx/d2dcc7d6839f6befc02e7f97cbbdb47dec33b4e18069c293145e05d786ec89fc