Transaction

ab5f019f6a45cf1237bfd44678a55681d501f13df3fe2e4b2a1ae92f3daec00d
Timestamp (utc)
2024-03-22 04:26:06
Fee Paid
0.00000011 BSV
(
0.00065448 BSV
-
0.00065437 BSV
)
Fee Rate
10.75 sat/KB
Version
1
Confirmations
95,788
Size Stats
1,023 B

2 Outputs

Total Output:
0.00065437 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post">I came to agree with Gavin about whitelisting when I realized how quickly new transaction types can be added.<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=2162.msg28434#msg28434">Quote from: nanotube on December 09, 2010, 06:19:05 AM</a></div><div class="quote">why not make it easier on everyone and just allow say, 64 or 128 bytes of random data in a transaction?<br/></div>That's already possible. &nbsp;&lt;pubkey&gt; OP_CHECKSIG. &nbsp;&lt;pubkey&gt; can be 33 to 120 bytes.<br/><br/>I also support a third transaction type for timestamp hash sized arbitrary data. &nbsp;There's no point not having one since you can already do it anyway. &nbsp;It would tell nodes they don't need to bother to index it.</div> text/html
    https://whatsonchain.com/tx/ab5f019f6a45cf1237bfd44678a55681d501f13df3fe2e4b2a1ae92f3daec00d