Transaction

526b8f1f20261dc28bee7ad8556f4a2f957e4ae4a0d6a69f76589cd7b19d0267
2024-03-24 22:29:25
0.00000013 BSV
(
0.00625065 BSV
-
0.00625052 BSV
)
10.3 sat/KB
1
76,316
1,262 B

2 Outputs

Total Output:
0.00625052 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMò<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=165.msg1373#msg1373">Quote from: theymos on June 05, 2010, 04:26:09 PM</a></div><div class="quote">Adding transactions to the block you're working on will slow down your generation rate<br/></div>The premise is false.&nbsp; Adding more transactions to the block you're working on does NOT slow down your generation rate.&nbsp; When generate is scanning hashes, it only hashes the header of the block, which is constant size.&nbsp; The header contains a hash of the transactions (the Merkle root) and is only updated occasionally.<br/><br/>If necessary I can write code to make nodes prefer not to use a block if it doesn't contain enough of the transactions they know about.&nbsp; A discouraged block would almost always fail to be included in the main chain, but would be accepted if it did get in.&nbsp; I doubt this will be necessary, since there's no real advantage for nodes not to include all transactions.</div> text/html
    https://whatsonchain.com/tx/526b8f1f20261dc28bee7ad8556f4a2f957e4ae4a0d6a69f76589cd7b19d0267