Transaction

3d7cd3d3e1f707d4e18fe8caaa6bc3c5a412bf392527f4433fe91ac9e5d7b3f1
Timestamp (utc)
2024-03-22 09:29:13
Fee Paid
0.00000013 BSV
(
0.00915554 BSV
-
0.00915541 BSV
)
Fee Rate
10.64 sat/KB
Version
1
Confirmations
94,098
Size Stats
1,221 B

2 Outputs

Total Output:
0.00915541 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/3d7cd3d3e1f707d4e18fe8caaa6bc3c5a412bf392527f4433fe91ac9e5d7b3f1