Transaction

Hash
fa235d1ad01fdd4374dd6a0e554f98f7ddd88bf5653408d83ffeafb0203dd99a
Block
629930 · 2020-04-07 14:38 · 211,872 confirmations
Data
memo-like
Size
272 bytes
Fee
272 sats (1 sat/B)

replied 1472d
Also defining a core use case and sticking to it can turn into a good answer to why not BCH instead of Sour? Which is always a good question I say for any tokens

Inputs (1)

Index
0
Previous Output
3045022100e50380b3c6137d15d67b95c550d47ca1f20b6b4e2efba1a5279d864dc372f60f02204eda0d479473a77b5e7701cf9e5d395ac1f276ac4bf48a5c4b8bbbe0d2d8543e41 0214879ce02e20d9870b4b1bb19b81b007f6b8b5f93acb505bb0a88c488b9ebd70

Outputs (3)

Index
0
Type
OP_RETURN
OP_RETURN 6d04 920c7cfb2dcbea27bc582799413df418b9183c3f16427eda531cdfdb757dc881
Index
1
OP_DUP OP_HASH160 c207ec66253450eb86b024b04bfa124b2563ed0f OP_EQUALVERIFY OP_CHECKSIG
Index
2
OP_DUP OP_HASH160 be0a62f70de42e451fd021549ab04658c7e00911 OP_EQUALVERIFY OP_CHECKSIG

Raw

01000000019e6d9a64e21c2929b797c628ee3d67ac8a2916bb5e5320b5a2e0a70ffadf9fe7010000006b483045022100e50380b3c6137d15d67b95c550d47ca1f20b6b4e2efba1a5279d864dc372f60f02204eda0d479473a77b5e7701cf9e5d395ac1f276ac4bf48a5c4b8bbbe0d2d8543e41210214879ce02e20d9870b4b1bb19b81b007f6b8b5f93acb505bb0a88c488b9ebd70ffffffff030000000000000000256a026d0420920c7cfb2dcbea27bc582799413df418b9183c3f16427eda531cdfdb757dc881a8610000000000001976a914c207ec66253450eb86b024b04bfa124b2563ed0f88ace5683000000000001976a914be0a62f70de42e451fd021549ab04658c7e0091188ac00000000