Memo - Bitcoin Social Network

Transaction

Hash

de0a38651641afe0dd4bb34ddbd962fbf25e12a9ee83c97624a3caac3f282bac

- Share
- Explore
- Block Explorer (BCH)
- Blockchair
- ViaWallet

Block

571859 · 2019-03-01 01:27 · 269,885 confirmations

Data

memo-like

Size

238 bytes

Fee

244 sats (1.02521014 sat/B)

SuperHacker.中国

liked 1874d

dixnorkel

replied 1874d

- Share
- Explore
- Block Explorer (BCH)
- Blockchair
- Member
- ViaWallet

SuperHacker.中国

This bug may cause some problem when timestamp is used by financial contract. i.e. timestamp based nLockTime

Not really a bug, there are protections like the ones I mentioned, and it's inherent/necessary to Bitcoin since the timestamp is used for hash variation as well

1 / 5 3

1,134

Inputs (1)

Index

Previous Output

04d8d57e...44dd370b:0

SuperHacker.中国

44,228

3045022100ddac14d30e2e95511c67005b77158ce449dbe8e65ed23e0f6a98ed2674839b320220249e31dae634fc33945aa8078903ae3842f78096efa168489c36c04884e3b24441 020f59a7750872a27a755f024418c481fad221e09e27e622622e6a2c2316733f7b

Outputs (2)

Index

Spent

fd55bbdd...5cb947a5:0

SuperHacker.中国

43,984

OP_DUP OP_HASH160 5d81beeee7aed1dbcd6f8128a86aa88f5882535e OP_EQUALVERIFY OP_CHECKSIG

Index

Type

OP_RETURN

OP_RETURN 6d04 214969f9810394577403259753db6d3effbbe9a55ac72f15064c29435ba65f2b

Raw

01000000010b37dd44abebb203b5602189d6734cb05e9e192153282ec61a589c5f7ed5d804000000006b483045022100ddac14d30e2e95511c67005b77158ce449dbe8e65ed23e0f6a98ed2674839b320220249e31dae634fc33945aa8078903ae3842f78096efa168489c36c04884e3b2444121020f59a7750872a27a755f024418c481fad221e09e27e622622e6a2c2316733f7bffffffff02d0ab0000000000001976a9145d81beeee7aed1dbcd6f8128a86aa88f5882535e88ac0000000000000000256a026d0420214969f9810394577403259753db6d3effbbe9a55ac72f15064c29435ba65f2b00000000