Transaction

0aa3ca511fb2e2647059d02e28cfd0e632a4c2e3d3b092bc860ca8d664c11b12
Timestamp (utc)
2024-03-27 18:25:09
Fee Paid
0.00000012 BSV
(
0.00720013 BSV
-
0.00720001 BSV
)
Fee Rate
10.43 sat/KB
Version
1
Confirmations
93,071
Size Stats
1,150 B

2 Outputs

Total Output:
0.00720001 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1332.msg14947#msg14947">Quote from: asdf on October 02, 2010, 04:56:08 AM</a></div><div class="quote">Pools offer the advantage that nodes can co-ordinate their hashing so that they aren't generating the same hashes as each other. It's not about "total hash/s", it's about "total unique hash/s". If everyone in the pool is assigned a subset of all hashes to work on (sizes based on each nodes average hash/s), then we'll guarantee that no hashes will be repeated.<br/></div><br/>This is already guaranteed because everyone has a unique public key in their block. You reminded me of another way that pools are bad, though: since everyone uses the same public key, they have to do weird things with extraNonce, which increases the size of the block header and makes generating more difficult for them.</div> text/html
    https://whatsonchain.com/tx/0aa3ca511fb2e2647059d02e28cfd0e632a4c2e3d3b092bc860ca8d664c11b12