Transaction

c86d21a448ffee4c74cf96bd8708ae2e60e9ada3e681504e2e8dbe52ded92b90
Timestamp (utc)
2024-03-30 02:00:14
Fee Paid
0.00000012 BSV
(
0.00251342 BSV
-
0.00251330 BSV
)
Fee Rate
10.73 sat/KB
Version
1
Confirmations
93,131
Size Stats
1,118 B

2 Outputs

Total Output:
0.00251330 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMb<div class="post">$ nice -n 15 ./poclbm.py &nbsp;--user=******** --pass=******** -f 60 -w 256<br/>No device specified, you may use -d to specify one of the following<br/><br/>found: 46380061, 26/10/2010 14:46<br/>found: 46380061, 26/10/2010 14:46<br/>17616 khash/s &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br/><br/>Found this just now. &nbsp;Why did it find the same block twice? &nbsp;Could it be there are, oh, like two threads repeating the same work?<br/><br/>EDIT: also, the main bitcoin client credited me with 50btc, one block, at 14:45.&nbsp; Total to my credit is just one block 50btc.&nbsp; What's going on?&nbsp; I looked through the source, and the RPC commands list.&nbsp; Where does the source poclbm.py tell the bitcoin client that it found a hash below the target?&nbsp; (I'm a python newbie).</div> text/html
    https://whatsonchain.com/tx/c86d21a448ffee4c74cf96bd8708ae2e60e9ada3e681504e2e8dbe52ded92b90