Transaction

2ff2acbd643c1b7130bdcbd71b14f60eceb16c8ec8a57d5d376b3d7f8b516d1a
Timestamp (utc)
2024-03-24 10:26:13
Fee Paid
0.00000010 BSV
(
0.01471582 BSV
-
0.01471572 BSV
)
Fee Rate
10.06 sat/KB
Version
1
Confirmations
101,205
Size Stats
994 B

2 Outputs

Total Output:
0.01471572 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMæ<div class="post">At the moment, if you make a payment to someone but they've wiped their wallet then the coins are irretrievably lost.<br/>Similarly, if the network is flooded with 0.01 fee transactions and you make an urgent payment but forget to include a higher fee then you can't reissue that payment backed by the same coins but with a fee.<br/><br/>If you could cause the current block number to be pushed on the stack and do some maths with it then you could implement a payment that must be spent by the recipient before a certain block number is reached or else the script would allow it to be spent again by the sender for example. <br/><br/>I suspect that this would be a very popular transaction mechanic.<br/><br/>ByteCoin</div> text/html
    https://whatsonchain.com/tx/2ff2acbd643c1b7130bdcbd71b14f60eceb16c8ec8a57d5d376b3d7f8b516d1a