Transaction: 7939b8e5490fbd01e8a42dd7e5ef6aff76a3b0fb

Included in block 6,874,940 at 2016/11/20 00:46:39 (UTC).

Transaction overview

Loading...
Transaction info
transaction_id 7939b8e5490fbd01e8a42dd7e5ef6aff76a3b0fb
ref_block_num 59,111
block_num6,874,940
ref_block_prefix 3,118,101,455
expiration2016/11/20T00:46:48
transaction_num 0
extensions[]
signatures 1f6370641a3c486fe713ad6354202cda9fc28f6f39aac5ce15f8d1f36dc82e7f2d75016ab2c88e449a57236126dabfff0060c723d9ce453156678e3e4b4522b025
operations
comment
"parent_author":"dantheman",<br>"parent_permlink":"re-charlieshrem-re-onthewayout-re-charlieshrem-announcing-steemmsg-encrypted-private-messages-on-the-steem-blockchain-20161119t215145456z",<br>"author":"charlieshrem",<br>"permlink":"re-dantheman-re-charlieshrem-re-onthewayout-re-charlieshrem-announcing-steemmsg-encrypted-private-messages-on-the-steem-blockchain-20161120t004635841z",<br>"title":"",<br>"body":"Yeh gareth was explaining to me it would it would make it impossible to automatically reconstruct our database from the blockchain though unless we encrypt the \"to\" field using our own key. He said \"it'll take a bit of time to engineer into a proper solution,<br> but the basic trick is to allow each user to store an arbitrary block of data in our database,<br> encrypted - and with deduplication\"",<br>"json_metadata":" \"tags\":[\"steem\" "
* The API used to generate this page is provided by @steemchiller.