Transaction

Hash
642961400bbcd2ce3e7a747dad0b092ef8a333cc27f237eb7b474cd7bc5601e6
Block
709499 · 2021-10-13 23:10 · 1,012 confirmations
Data
memo-message
Size
302 bytes
Fee
303 sats (1.00331128 sat/B)

17BMz3PLLp76zak8
7d
First post on the chain - is an OP_RETURN to store arbitrary data on the blockchain a good idea?

Inputs (1)

Index
0
Previous Output
17BMz3PLLp76zak8
3044022047df5d59c589b815df99ceeda1cb4a5b38068161a8acaebb7e0e3605e9f6808c022034e601d726ad41bf1172a211b15a32df36199bd09176d0f1745c49d2ba90eec241 02bb15451f0d8815e9c1f94eabd7a269fe4f5ba6007dbbc937a69128d40c3c7462

Outputs (2)

Index
0
Type
OP_RETURN
OP_RETURN 6d02 466972737420706f7374206f6e2074686520636861696e202d20697320616e204f505f52455455524e20746f2073746f7265206172626974726172792064617461206f6e2074686520626c6f636b636861696e206120676f6f6420696465613f
Index
1
OP_DUP OP_HASH160 b1333c4af967887b3fa270e4712caec73469f49a OP_EQUALVERIFY OP_CHECKSIG

Raw

0100000001b049139a820b9d04e63d54f824b0811e220f60f7c250210c18ef455ec75334a5000000006a473044022047df5d59c589b815df99ceeda1cb4a5b38068161a8acaebb7e0e3605e9f6808c022034e601d726ad41bf1172a211b15a32df36199bd09176d0f1745c49d2ba90eec2412102bb15451f0d8815e9c1f94eabd7a269fe4f5ba6007dbbc937a69128d40c3c7462ffffffff020000000000000000666a026d024c60466972737420706f7374206f6e2074686520636861696e202d20697320616e204f505f52455455524e20746f2073746f7265206172626974726172792064617461206f6e2074686520626c6f636b636861696e206120676f6f6420696465613f5b100000000000001976a914b1333c4af967887b3fa270e4712caec73469f49a88ac00000000