Transaction

6a161ef02faf2fbcd1a48d4967bbf5cbd6f057ebec615b86deb3a8d312261cc5
Timestamp (utc)
2024-03-24 17:15:38
Fee Paid
0.00000034 BSV
(
0.00981099 BSV
-
0.00981065 BSV
)
Fee Rate
10.19 sat/KB
Version
1
Confirmations
97,452
Size Stats
3,335 B

2 Outputs

Total Output:
0.00981065 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM <div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=325.msg2916#msg2916">Quote from: InterArmaEnimSil on July 14, 2010, 07:07:03 PM</a></div><div class="quote">Okay - if everyone's machines are working on a hash to a different problem, then I can see how luck would be a factor. &nbsp;However, what is the source of the variation between the problem my machine is working on, the problem yours is, etc? &nbsp;One reply earlier seemed to imply that it had to do with transactions in which the individual recently took part....but what about those of us not taking part in any recent transactions? (My most recent one is at least two days old now)<br/></div>In terms of Coin Generation, you need only be connected to the network. That's all that is needed for your computer to broadcast "I found it!!" message and for other computers to check if it's valid. Since blocks are being generated on a constant basis, doing offline Coin generation won't be practical. Because if 2 days ago your computer found a block, but so did mine and my PC was online the whole time, mine will be proclaimed the winner/owner of that Coin by the network as a whole. Your PC comes in 2 days later and broadcast that it has the same solution and the other computers will just snide a "too late, XYZ already solved it, better luck next time".<br/><br/>In terms of variation between problems, when a block is found, everyone starts on the next block. So if your computer was only 1% towards solving block 68000 and got the message "XYZ solved the block 68000 just a few minutes ago", your PC thinks "well, on to the next one". It doesn't waste CPU trying to solve a block that was already solved by someone else. That's where the verification part comes in. Otherwise, someone would just hack together a client that broadcast "I solved block 68000, 680001, 68002, etc" to claim ownership of the entire range. When a client says it solved a block, all the other computers say "ok, well prove it then, send me your results". When enough of them talk to each other about it, they will agree that "yes, your PC solved block 68000, you are the new owner, congratulations".<br/><br/>The key part is that it takes hours/days for our PCs to solve a block, but only milliseconds for everyone else to check if it's true. That prevents a "fake block found" attack from happening on the network.<br/><br/>Another example, you have a room with hundreds of people in it. Everyone is given a randomly mixed up Rubix cube to solve. The first one to solve his/her cube gets 50 coin.<br/><br/>Now if someone shouts "I solved it", it won't take but a mere glance from the surrounding people to tell if it's true or not (solid colors on all sides) If someone shouts "I solved it" and it's still a jumbled mess, well everyone just ignores that person and continues on. The first person who solves it for "real" wins the prize and then everyone throws away their current Rubix cube and a bunch more randomly mixed Rubix cubes drop from the ceiling to start the process all over again.</div> text/html
    https://whatsonchain.com/tx/6a161ef02faf2fbcd1a48d4967bbf5cbd6f057ebec615b86deb3a8d312261cc5