Transaction

a5b1fbd61fc7ea2b5d4bff00b42e62af0de6e0dbe49c45bfd13daa8f6877cf72
Timestamp (utc)
2024-03-23 21:30:42
Fee Paid
0.00000013 BSV
(
0.02337583 BSV
-
0.02337570 BSV
)
Fee Rate
10.68 sat/KB
Version
1
Confirmations
102,229
Size Stats
1,217 B

2 Outputs

Total Output:
0.02337570 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÄ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1976.msg24928#msg24928">Quote from: slush on November 27, 2010, 06:58:19 PM</a></div><div class="quote">Oh, so when I got work from coordinator which leads to winning hash, I cannot send it to bitcoin network as "my own" hash?</div><br/>In a pooled mining situation, the winning hash <b>cannot</b> be used as "your own".<br/><br/>The hash incorporates all of the transactions in the block, including the one that pays 50 BTC to the generator.<br/><br/>If you are hashing for pooled generation, the winning hash is only useful to the pool.<br/><br/>If you are hashing for yourself, then obviously the winning hash is useful to you. But in that case the "low-difficulty" hashes that you generate are useless to the pool, so the pool will not pay you a share of the generated 50 BTC.<br/><br/>It is a solved problem to prevent cheating with pooled generation.<br/><br/></div> text/html
    https://whatsonchain.com/tx/a5b1fbd61fc7ea2b5d4bff00b42e62af0de6e0dbe49c45bfd13daa8f6877cf72