Transaction

f1b9ea7351d6bb4d2a1e1d6c0b7dfa3822ee8a8ad30e1656cbc098ea77ae32cf
Timestamp (utc)
2024-03-24 16:17:04
Fee Paid
0.00000010 BSV
(
0.01048579 BSV
-
0.01048569 BSV
)
Fee Rate
10.22 sat/KB
Version
1
Confirmations
97,300
Size Stats
978 B

2 Outputs

Total Output:
0.01048569 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÕ<div class="post">Satoshi,<br/><br/>The "block lock" is an interesting idea, and I'll have to think more about it. &nbsp;However, it's important that you don't lock all the way up the very latest block. &nbsp;Otherwise, the attacker could generate a fake block (or a few) right before you happen to lock it, and then his attack would be far easier than it would have been without the block lock.<br/><br/>Instead, you should only lock in everything except the last thousand or so blocks (the exact number should be a subject of future inquiry). &nbsp;Maybe this is actually what you did?<br/><br/>Also, I'm assuming that the block lock means that the blocks will also come prepackaged with the client. &nbsp;Is this so?</div> text/html
    https://whatsonchain.com/tx/f1b9ea7351d6bb4d2a1e1d6c0b7dfa3822ee8a8ad30e1656cbc098ea77ae32cf