$ .../datacoind getdata 5e0adc631cab6f9040e125a5eed5c87803c4e95c2e734a1bc3d6c36f56cbb94e
TVJdLTBAXy9EV2MxZjRiZGFmY2M4Y2RmMTU0MDIxZjI4NzEyYzNkNjMzLDZmMDNiYjJhNGVlMzE4NzM 2YTc4OTlhZDI0MDVhNDE1LA==
It seems that transaction does not contain the original gif file. It seems it contains MD5 signature of the external file.
"TVJdLTBAXy9EV2MxZjRiZGFmY2M4Y2RmMTU0MDIxZjI4NzEyYzNkNjMzLDZmMDNiYjJhNGVlMzE4NzM
2YTc4OTlhZDI0MDVhNDE1LA==" is base64 encoded.
After decode "TVJdLTBAXy9EV2MxZjRiZGFmY2M4Y2RmMTU0MDIxZjI4NzEyYzNkNjMzLDZmMDNiYjJhNGVlMzE4NzM
2YTc4OTlhZDI0MDVhNDE1LA=="
turns into "MR]-0@_/DW
c1f4bdafcc8cdf154021f28712c3d633,
6f03bb2a4ee318736a7899ad2405a415,"
It perfectly corresponds to bytestamp's info of that transaction: "MD5 in this transaction: c1f4bdafcc8cdf154021f28712c3d633 - MD5 of the note: 6f03bb2a4ee318736a7899ad2405a415"
It seems that "MR]-0@_/DW
c1f4bdafcc8cdf154021f28712c3d633,
6f03bb2a4ee318736a7899ad2405a415," is some sort of data formatting for saving file signatures.