Transaction

Hash
1ddba3decf34e42fb6bffa6abd07728c4a080d67e4f268d41de6bee382502aa7
Block
533363 · 2018-06-05 10:12 · 317,199 confirmations
Data
memo-reply
Size
391 bytes
Fee
393 sats (1.00511503 sat/B)

replied 2212d
You could store a hash of the message on-chain, so the tx would only verify a message, not store it. This way, if logs get leaked, they can be verified.

Inputs (1)

Index
0
Previous Output
3044022054e71498bf2de028c3db6fbd974de965b9a3c7add5b7880d9c9d49d4279afcd6022074107636ffc9f4e7ef3fde016b797f59fde2b4bcbff109e97cc2a3b26bfc827141 036384ccc6b48a2fb99d5bab82da9ed3cc1d920ceb9128fa10ecea439f18167c2e

Outputs (2)

Index
0
OP_DUP OP_HASH160 9d79e79cc6dd8fe14918df054f6acfe6d96ee467 OP_EQUALVERIFY OP_CHECKSIG
Index
1
Type
OP_RETURN
OP_RETURN 6d03 40ba9c408504fcd38bca00671cde26bfe7663ea6c01d8e170984979fbbd9a549 596f7520636f756c642073746f726520612068617368206f6620746865206d657373616765206f6e2d636861696e2c20736f2074686520747820776f756c64206f6e6c79207665726966792061206d6573736167652c206e6f742073746f72652069742e2054686973207761792c206966206c6f677320676574206c65616b65642c20746865792063616e2062652076657269666965642e

Raw

0100000001b5cbccaee0e30cf593a27c3cc0d52902e2928af11e8a6cec1ba00938bf054319020000006a473044022054e71498bf2de028c3db6fbd974de965b9a3c7add5b7880d9c9d49d4279afcd6022074107636ffc9f4e7ef3fde016b797f59fde2b4bcbff109e97cc2a3b26bfc82714121036384ccc6b48a2fb99d5bab82da9ed3cc1d920ceb9128fa10ecea439f18167c2effffffff02c11e0000000000001976a9149d79e79cc6dd8fe14918df054f6acfe6d96ee46788ac0000000000000000bf6a026d032040ba9c408504fcd38bca00671cde26bfe7663ea6c01d8e170984979fbbd9a5494c98596f7520636f756c642073746f726520612068617368206f6620746865206d657373616765206f6e2d636861696e2c20736f2074686520747820776f756c64206f6e6c79207665726966792061206d6573736167652c206e6f742073746f72652069742e2054686973207761792c206966206c6f677320676574206c65616b65642c20746865792063616e2062652076657269666965642e00000000