Transaction

Hash
abadef639b866e49d61d7b7c18c3ca03e062ee554856670d9611ce6f669f4e12
Block
584504 · 2019-05-29 06:50 · 266,073 confirmations
Data
memo-reply
Size
392 bytes
Fee
399 sats (1.01785719 sat/B)

replied 1854d
Yes, the most straightforward approach to solving that would be to code it up across the full node clients so that they don't have to apply it manually.

Inputs (1)

Index
0
Previous Output
3045022100d3b1b143f01f3a3ae790bd150abf25b59953af61baa32427a10a1c1cce7af93502206664289ed61d2d3e843c02a0c4ef0197168ef45df9c78cbac234f15d5b7b9e4f41 02708ca57b70f564ee7cc29db11e7578e0a474f93e65455a08b46d8cd1330d57cd

Outputs (2)

Index
0
OP_DUP OP_HASH160 910a0201437732db6cbb13083adbb62c7ab96004 OP_EQUALVERIFY OP_CHECKSIG
Index
1
Type
OP_RETURN
OP_RETURN 6d03 7eeed8a610d5d80b49f417cd279849212bba51ca656a82ef2f824eeeaf106746 5965732c20746865206d6f7374207374726169676874666f727761726420617070726f61636820746f20736f6c76696e67207468617420776f756c6420626520746f20636f6465206974207570206163726f7373207468652066756c6c206e6f646520636c69656e747320736f2074686174207468657920646f6e2774206861766520746f206170706c79206974206d616e75616c6c792e

Raw

01000000011e6dd3038f8e15bf27b014046d9b96f5873b4800cfb530e12a98a54891c39089000000006b483045022100d3b1b143f01f3a3ae790bd150abf25b59953af61baa32427a10a1c1cce7af93502206664289ed61d2d3e843c02a0c4ef0197168ef45df9c78cbac234f15d5b7b9e4f412102708ca57b70f564ee7cc29db11e7578e0a474f93e65455a08b46d8cd1330d57cdffffffff0218240d00000000001976a914910a0201437732db6cbb13083adbb62c7ab9600488ac0000000000000000bf6a026d03207eeed8a610d5d80b49f417cd279849212bba51ca656a82ef2f824eeeaf1067464c985965732c20746865206d6f7374207374726169676874666f727761726420617070726f61636820746f20736f6c76696e67207468617420776f756c6420626520746f20636f6465206974207570206163726f7373207468652066756c6c206e6f646520636c69656e747320736f2074686174207468657920646f6e2774206861766520746f206170706c79206974206d616e75616c6c792e00000000