Tx ed8b2f45ae3e1ae5b2ca8fe3df0aa4391dc3ef73@41142337
Included in block
41,142,337
at 2020-02-26 00:27:06 (UTC)
Raw transaction
| ref_block_num | 51,248 |
|---|
| ref_block_prefix | 3,287,580,942 |
|---|
| expiration | 2020-02-26 00:37:03 |
|---|
| operations | | 0. | | 0. | comment |
|---|
| 1. | | parent_author | joebrochin |
|---|
| parent_permlink | re-fullcolorpy-q694l5 |
|---|
| author | mrosenquist |
|---|
| permlink | q6a993 |
|---|
| title | "" |
|---|
| body | "@joebrochin From a cybersecurity perspective, I would treat Telegram like any other social media platform. There is little in the way of verifying to whom you are communicating with, if they see the message (non-repudiation), or that the data you send is private in any reasonable way. It is essentially an electronic bulletin board. It can be hacked, spoofed, and manipulated by those with malicious intent (just like other online social networks). I recommend you only share what you would want to be public (even when using direct messages)." |
|---|
| json_metadata | {"users":["joebrochin"],"app":"steemit/0.2"} |
|---|
|
|---|
|
|---|
|
|---|
| extensions | [] |
|---|
| signatures | | 0. | 1f47d80683d0c6c477fdffbae150ffb60c8b57b22dc88fb0e35f5cf62211d4466425aad093f97b19213259844815afb5b62d4d1b1e14e31c1149e9cb6b97b3fbcd |
|---|
|
|---|
| transaction_id | ed8b2f45ae3e1ae5b2ca8fe3df0aa4391dc3ef73 |
|---|
| block_num | 41,142,337 |
|---|
| transaction_num | 21 |
|---|