Tx 0702225fc43f0baafa629c3d94e107cb32932a3a@50553445
Included in block
50,553,445
at 2021-01-18 17:30:24 (UTC)
Raw transaction
| ref_block_num | 25,188 |
|---|
| ref_block_prefix | 2,722,241,975 |
|---|
| expiration | 2021-01-18 17:31:21 |
|---|
| operations | | 0. | | 0. | comment |
|---|
| 1. | | parent_author | practicalthought |
|---|
| parent_permlink | qn53ye |
|---|
| author | cmplxty |
|---|
| permlink | re-practicalthought-2021118t123021746z |
|---|
| title | "" |
|---|
| body | "The way I understand it is that the chrome extension encrypts the key strings with a password you use to unlock and sign transactions. The software asks for just your posting key or active key so it’s minimal required to do most things. If anything suspicious happens from hacking to your computer they can’t do anything on hive unless they know your unlock password for hive keychain. I don’t know if a key logger captures the password but it’s safer than broadcasting the transaction to a third party server that then signs it for you. I’m not too technical for this particular stuff but it’s safer in my experience! Less vectors of attack.
If you’re concerned with protection try getting the Tor browser or Brave. I use brave personally and it’s great with the upgraded security measures. " |
|---|
| json_metadata | {"tags":["ecency"],"app":"ecency/3.0.12-mobile","format":"markdown+html"} |
|---|
|
|---|
|
|---|
|
|---|
| extensions | [] |
|---|
| signatures | | 0. | 201464d949a19095ea91a2f2bb7cb640445618882bb37b93f9366ce60417f3e400084b6ab5b9ed821bee37cbc417070593f96e5c72ff13a6bb120b895d2eb53e12 |
|---|
|
|---|
| transaction_id | 0702225fc43f0baafa629c3d94e107cb32932a3a |
|---|
| block_num | 50,553,445 |
|---|
| transaction_num | 36 |
|---|
hiveblocks