Transaction

3cf1a8a0b43e7a8bf5bc6879ea24e9d3a52a003d5d02cfce41b7beb151a76aa8
Timestamp (utc)
2024-03-23 14:22:59
Fee Paid
0.00000013 BSV
(
0.02819942 BSV
-
0.02819929 BSV
)
Fee Rate
10.63 sat/KB
Version
1
Confirmations
97,725
Size Stats
1,222 B

2 Outputs

Total Output:
0.02819929 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÉ<div class="post">consider also that it's possible to encode data into the bitcoin blockchain already, merely by specially crafting the transaction. (See the 'first' option on <a href="http://privwiki.dreamhosters.com/wiki/Bitcoin_DNS_System_Proposal#Overcoming_potential_resistance_bitcoin_developers.2Fcommunity">http://privwiki.dreamhosters.com/wiki/Bitcoin_DNS_System_Proposal#Overcoming_potential_resistance_bitcoin_developers.2Fcommunity</a> ). <br/><br/>alternatively, only timestamping and proof of expense (i.e., a regular transaction with a fee) may be used, pushing off the actual data storage off to external service (see 'third' option, ibid.)<br/><br/>but why not make it easier on everyone and just allow say, 64 or 128 bytes of random data in a transaction? it seems that in the net, these side-band uses of bitcoin will only serve to increase the security of the network, by increasing the mining incentive, and bringing on more generation power.</div> text/html
    https://whatsonchain.com/tx/3cf1a8a0b43e7a8bf5bc6879ea24e9d3a52a003d5d02cfce41b7beb151a76aa8