@a-diddy
25Software, EE, Crypto, Snowboarding, Photography, Alchemy and Ascension
steemit.com/@a-diddyVOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.034USD
STEEM
0.001STEEM
SBD
0.000SBD
Effective Power
5.001SP
├── Own SP
0.632SP
└── Incoming DelegationsDeleg
+4.369SP
Detailed Balance
| STEEM | ||
| balance | 0.001STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.632SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.369SP | SP |
| Effective Power | 5.001SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.000SBD | SBD |
{
"balance": "0.001 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1028.726930 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7114.932876 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | a-diddy |
| id | 409543 |
| rank | 647,891 |
| reputation | 0 |
| created | 2017-10-13T16:31:39 |
| recovery_account | steem |
| proxy | None |
| post_count | 1 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-02-15T01:43:57 |
| last_root_post | 2018-02-15T01:43:57 |
| last_vote_time | 2017-10-13T16:52:18 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.001 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1028.726930 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7114.932876 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 2017-10-13T16:36:18 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 409543,
"name": "a-diddy",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7sgRawejtQzm1zF9wcMv4MGBSRDddWR7CAd5QG9PsQ9vy8JL7m",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7KWhqYeFXNAG7srPtDAxJG2mJMzUL3n1HEHrTjr8y57nUwPHVJ",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5uc2PotR6PKVP9x1ZS2i5th4561C6tqnpmPXahKwrf4jU9XcQL",
1
]
]
},
"memo_key": "STM8cgFdqKxoCZVNuPQZxShW6DMLYQ459N3KTWNdnx8jFutEAQqUx",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/852573150155907072/hPoWclvw_400x400.jpg\",\"cover_image\":\"https://pbs.twimg.com/profile_banners/20545714/1492104252/1500x500\",\"name\":\"Austin [NO2X]\",\"about\":\"Software, EE, Crypto, Snowboarding, Photography, Alchemy and Ascension\",\"location\":\"Orange County, CA\"}}",
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/852573150155907072/hPoWclvw_400x400.jpg\",\"cover_image\":\"https://pbs.twimg.com/profile_banners/20545714/1492104252/1500x500\",\"name\":\"Austin [NO2X]\",\"about\":\"Software, EE, Crypto, Snowboarding, Photography, Alchemy and Ascension\",\"location\":\"Orange County, CA\"}}",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2017-10-13T16:36:18",
"created": "2017-10-13T16:31:39",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 1,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779050721
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779050721
},
"voting_power": 0,
"balance": "0.001 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"vesting_shares": "1028.726930 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7114.932876 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 0,
"posting_rewards": 0,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-02-15T01:43:57",
"last_root_post": "2018-02-15T01:43:57",
"last_vote_time": "2017-10-13T16:52:18",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 0,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 647891
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2026/05/17 20:45:21
2026/05/17 20:45:21
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 7114.932876 VESTS |
| Transaction Info | Block #106139269/Trx 2ae73333358a5522eea6ff1b7bc36cc8e49f4152 |
View Raw JSON Data
{
"trx_id": "2ae73333358a5522eea6ff1b7bc36cc8e49f4152",
"block": 106139269,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-17T20:45:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "7114.932876 VESTS"
}
]
}2026/05/11 16:04:36
2026/05/11 16:04:36
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 4402.722471 VESTS |
| Transaction Info | Block #105961636/Trx c64488735f4c64d6e84305ae05be934fd2edfa34 |
View Raw JSON Data
{
"trx_id": "c64488735f4c64d6e84305ae05be934fd2edfa34",
"block": 105961636,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-11T16:04:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "4402.722471 VESTS"
}
]
}2026/04/25 20:11:39
2026/04/25 20:11:39
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 7127.448632 VESTS |
| Transaction Info | Block #105507019/Trx ee98f362d107bd12bde35363544c42ec0deaf56a |
View Raw JSON Data
{
"trx_id": "ee98f362d107bd12bde35363544c42ec0deaf56a",
"block": 105507019,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-25T20:11:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "7127.448632 VESTS"
}
]
}2026/01/22 22:24:27
2026/01/22 22:24:27
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 4444.269290 VESTS |
| Transaction Info | Block #102840562/Trx a68546b26d75e20a364c6cb25a2f05bd765e4a3e |
View Raw JSON Data
{
"trx_id": "a68546b26d75e20a364c6cb25a2f05bd765e4a3e",
"block": 102840562,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-22T22:24:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "4444.269290 VESTS"
}
]
}2024/12/16 17:45:57
2024/12/16 17:45:57
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 4608.488487 VESTS |
| Transaction Info | Block #91287015/Trx e665431e828f48b4f867136a76a7cd2a93b001d1 |
View Raw JSON Data
{
"trx_id": "e665431e828f48b4f867136a76a7cd2a93b001d1",
"block": 91287015,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-16T17:45:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "4608.488487 VESTS"
}
]
}2023/11/13 09:31:42
2023/11/13 09:31:42
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 4777.624933 VESTS |
| Transaction Info | Block #79841295/Trx 1205c269b66315fbccb9b4df2da75901e209db66 |
View Raw JSON Data
{
"trx_id": "1205c269b66315fbccb9b4df2da75901e209db66",
"block": 79841295,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-13T09:31:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "4777.624933 VESTS"
}
]
}2023/09/21 17:41:57
2023/09/21 17:41:57
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 7714.900805 VESTS |
| Transaction Info | Block #78342892/Trx e60102eec78710a14a6f8b47667226df8f60cac8 |
View Raw JSON Data
{
"trx_id": "e60102eec78710a14a6f8b47667226df8f60cac8",
"block": 78342892,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-21T17:41:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "7714.900805 VESTS"
}
]
}2022/11/03 07:58:36
2022/11/03 07:58:36
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 7936.582243 VESTS |
| Transaction Info | Block #69108807/Trx 8b7deb223d67820d5187e7ca828adac5db9a55a8 |
View Raw JSON Data
{
"trx_id": "8b7deb223d67820d5187e7ca828adac5db9a55a8",
"block": 69108807,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T07:58:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "7936.582243 VESTS"
}
]
}2022/01/17 07:36:15
2022/01/17 07:36:15
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 8157.115474 VESTS |
| Transaction Info | Block #60805415/Trx ed6700207dc686bf30615a2fb862a8113b86cf06 |
View Raw JSON Data
{
"trx_id": "ed6700207dc686bf30615a2fb862a8113b86cf06",
"block": 60805415,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-17T07:36:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "8157.115474 VESTS"
}
]
}2021/06/13 21:39:54
2021/06/13 21:39:54
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 8340.884132 VESTS |
| Transaction Info | Block #54603974/Trx 4d34edecfbde4be0f6bc92eb7b476624929d923f |
View Raw JSON Data
{
"trx_id": "4d34edecfbde4be0f6bc92eb7b476624929d923f",
"block": 54603974,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-13T21:39:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "8340.884132 VESTS"
}
]
}2020/12/11 08:03:21
2020/12/11 08:03:21
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 8528.306106 VESTS |
| Transaction Info | Block #49351562/Trx 3ea37baa9ca66517e9f2d90a020e17a4ede49361 |
View Raw JSON Data
{
"trx_id": "3ea37baa9ca66517e9f2d90a020e17a4ede49361",
"block": 49351562,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T08:03:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "8528.306106 VESTS"
}
]
}2020/12/06 01:40:45
2020/12/06 01:40:45
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49203132/Trx f97d6c8dd82d237c18cd956f1c1f5786ee698cd7 |
View Raw JSON Data
{
"trx_id": "f97d6c8dd82d237c18cd956f1c1f5786ee698cd7",
"block": 49203132,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T01:40:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "1912.543513 VESTS"
}
]
}2020/11/25 14:19:12
2020/11/25 14:19:12
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 8545.432723 VESTS |
| Transaction Info | Block #48905944/Trx e23dcd0b437205f25712c4738b5c18e4a0baf971 |
View Raw JSON Data
{
"trx_id": "e23dcd0b437205f25712c4738b5c18e4a0baf971",
"block": 48905944,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-25T14:19:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "8545.432723 VESTS"
}
]
}2020/05/09 02:35:12
2020/05/09 02:35:12
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 8737.319319 VESTS |
| Transaction Info | Block #43213342/Trx cabdcfb2bf1d71a565546ba1c430f28c5f6e37fe |
View Raw JSON Data
{
"trx_id": "cabdcfb2bf1d71a565546ba1c430f28c5f6e37fe",
"block": 43213342,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T02:35:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "8737.319319 VESTS"
}
]
}2020/05/08 05:42:30
2020/05/08 05:42:30
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43188872/Trx aea48dfe2e23ce563eb8a5032615ce5a025db024 |
View Raw JSON Data
{
"trx_id": "aea48dfe2e23ce563eb8a5032615ce5a025db024",
"block": 43188872,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T05:42:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "1953.311140 VESTS"
}
]
}2019/10/13 17:42:27
2019/10/13 17:42:27
| parent author | a-diddy |
| parent permlink | using-custom-elements-in-an-angular-typescript-project |
| author | steemitboard |
| permlink | steemitboard-notify-a-diddy-20191013t174227000z |
| title | |
| body | Congratulations @a-diddy! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@a-diddy/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@a-diddy) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=a-diddy)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemfest/@steemitboard/the-new-steemfest-badge-is-ready"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmRUkELn2Fd13pWFkmWU2wBMMx39EBX5V3cHBEZ2d7f3Ve/image.png"></a></td><td><a href="https://steemit.com/steemfest/@steemitboard/the-new-steemfest-badge-is-ready">The new SteemFest⁴ badge is ready</a></td></tr></table> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #37253895/Trx 33681770fc3d5ec5941915a452960117d87392c5 |
View Raw JSON Data
{
"trx_id": "33681770fc3d5ec5941915a452960117d87392c5",
"block": 37253895,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-13T17:42:27",
"op": [
"comment",
{
"parent_author": "a-diddy",
"parent_permlink": "using-custom-elements-in-an-angular-typescript-project",
"author": "steemitboard",
"permlink": "steemitboard-notify-a-diddy-20191013t174227000z",
"title": "",
"body": "Congratulations @a-diddy! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@a-diddy/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@a-diddy) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=a-diddy)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemfest/@steemitboard/the-new-steemfest-badge-is-ready\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmRUkELn2Fd13pWFkmWU2wBMMx39EBX5V3cHBEZ2d7f3Ve/image.png\"></a></td><td><a href=\"https://steemit.com/steemfest/@steemitboard/the-new-steemfest-badge-is-ready\">The new SteemFest⁴ badge is ready</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}2019/09/18 04:19:03
2019/09/18 04:19:03
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 8869.933749 VESTS |
| Transaction Info | Block #36519359/Trx 86331d9af5e8e87179c98556ead3737aae1ed7bb |
View Raw JSON Data
{
"trx_id": "86331d9af5e8e87179c98556ead3737aae1ed7bb",
"block": 36519359,
"trx_in_block": 26,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-09-18T04:19:03",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "8869.933749 VESTS"
}
]
}2018/10/08 15:28:54
2018/10/08 15:28:54
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 9067.954661 VESTS |
| Transaction Info | Block #26631302/Trx 19d2ee5d7d29ee4a196e3327e6020c691776dcdd |
View Raw JSON Data
{
"trx_id": "19d2ee5d7d29ee4a196e3327e6020c691776dcdd",
"block": 26631302,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-10-08T15:28:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "9067.954661 VESTS"
}
]
}2018/09/26 16:33:24
2018/09/26 16:33:24
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 60619.029150 VESTS |
| Transaction Info | Block #26287256/Trx 3f47eea5017525192c9dee2dd71b99eee6abb3ba |
View Raw JSON Data
{
"trx_id": "3f47eea5017525192c9dee2dd71b99eee6abb3ba",
"block": 26287256,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-26T16:33:24",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "60619.029150 VESTS"
}
]
}2018/07/09 16:43:15
2018/07/09 16:43:15
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 9116.937070 VESTS |
| Transaction Info | Block #24029544/Trx 1d8730cf07c642a9589801ecb9930341a1a04ba1 |
View Raw JSON Data
{
"trx_id": "1d8730cf07c642a9589801ecb9930341a1a04ba1",
"block": 24029544,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-09T16:43:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "9116.937070 VESTS"
}
]
}2018/04/21 20:37:21
2018/04/21 20:37:21
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 29533.441018 VESTS |
| Transaction Info | Block #21771035/Trx f4ca4ba26bdd6b4ece4294e285f40730ccb63e27 |
View Raw JSON Data
{
"trx_id": "f4ca4ba26bdd6b4ece4294e285f40730ccb63e27",
"block": 21771035,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-21T20:37:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "29533.441018 VESTS"
}
]
}a-diddycustom json: follow2018/04/09 15:45:36
a-diddycustom json: follow
2018/04/09 15:45:36
| required auths | [] |
| required posting auths | ["a-diddy"] |
| id | follow |
| json | ["reblog",{"account":"a-diddy","author":"elizbethleavos","permlink":"a-retrospective-look-at-the-work-wikileaks-made-possible-as-assange-remains-silenced"}] |
| Transaction Info | Block #21419657/Trx 40c457881a529a32ecea4f5883c94a4ecbadd199 |
View Raw JSON Data
{
"trx_id": "40c457881a529a32ecea4f5883c94a4ecbadd199",
"block": 21419657,
"trx_in_block": 52,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-09T15:45:36",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"a-diddy"
],
"id": "follow",
"json": "[\"reblog\",{\"account\":\"a-diddy\",\"author\":\"elizbethleavos\",\"permlink\":\"a-retrospective-look-at-the-work-wikileaks-made-possible-as-assange-remains-silenced\"}]"
}
]
}2018/02/15 04:54:03
2018/02/15 04:54:03
| parent author | a-diddy |
| parent permlink | using-custom-elements-in-an-angular-typescript-project |
| author | steemitboard |
| permlink | steemitboard-notify-a-diddy-20180215t045403000z |
| title | |
| body | Congratulations @a-diddy! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@a-diddy) You published your First Post Click on any badge to view your own Board of Honor on SteemitBoard. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| Transaction Info | Block #19882001/Trx a71a976762769ed18a0452dbc461dcce078e2ae6 |
View Raw JSON Data
{
"trx_id": "a71a976762769ed18a0452dbc461dcce078e2ae6",
"block": 19882001,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-15T04:54:03",
"op": [
"comment",
{
"parent_author": "a-diddy",
"parent_permlink": "using-custom-elements-in-an-angular-typescript-project",
"author": "steemitboard",
"permlink": "steemitboard-notify-a-diddy-20180215t045403000z",
"title": "",
"body": "Congratulations @a-diddy! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@a-diddy) You published your First Post\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}"
}
]
}a-diddypublished a new post: using-custom-elements-in-an-angular-typescript-project2018/02/15 01:43:57
a-diddypublished a new post: using-custom-elements-in-an-angular-typescript-project
2018/02/15 01:43:57
| parent author | |
| parent permlink | angular |
| author | a-diddy |
| permlink | using-custom-elements-in-an-angular-typescript-project |
| title | Using Custom Elements in an Angular TypeScript Project |
| body | # Introduction Custom web elements are the future of web development. Their ease of use and modularization of HTML, CSS and JS make them perfect for sharing in multiple applications with as little work as possible. Importing a custom element into a project is as easy adding a CSS file. Then use them like any other HTML element, passing configuration and properties into them without the need to write any JS. ````html <link rel="import" href="../../../../assets/oc-mt/src/app/polymerComponents/mt-img-suite/mt-img-suite.html"/> <mt-img-suite editor-id="editorSuite" image-editor-config-url="../../../../assets/config/hiddenButtons-image-editor-config.json" stylesheet="../../../../assets/css/img-editor-MVI.css" mobile-controls="false" edit-eyes="true" ></mt-img-suite> ```` Custom elements are not only a great way to encapsulate and share modularized functions and features, they’re also part of the [HTML5 specification](https://www.w3.org/TR/custom-elements/). That means they can be used in any web application that adheres to web standards. Unfortunately, some frameworks don’t fully play by the rules and need some tweaking to perform as one would expect. Among the worst offenders of all time is AngularJS. However, fortunately, custom elements are so powerful that even the Angular developers yielded to the custom element revolution and decided to embrace their usage. This was one of the main reasons Angular 2 was created. Basically, it was a near complete rewrite of the project to utilize more of the browser’s built in ability to manage custom elements, which is nearly 10 times more efficient than AngularJS's parsing approach. Today, Angular 2 plays along very nicely with custom elements. While Angular still comes with its own quirks, terminology and approaches, custom elements can be used in any Angular project without any limitations. The below topics discuss the main hurdles I’ve come across while using custom elements in an Angular 5 project developed in TypeScript. While it may seem like a lot, I’m convinced that once these quirks are known and addressed, TypeScript, Angular and the custom elements can all play nicely without any limitations. # Static Assets TypeScript uses dynamic dependency injection during build/run time and, using Webpack, concatenates the dependencies into a series of bundles that are downloaded and executed in a certain order. This is a great approach for JS files and for HTML files, which get transferred as string data and parsed as needed. However, the parsing performed on the client does not appear to support HTML files that have JS `<script>` elements in them and vice-versa. The `<script>` content will be interpreted as a string when the HTML is injected in the DOM. The workaround to this is to place custom HTML5 elements inside the static asset directory, “src/assets/”, with all of their dependencies. In summary, within the “assets” directory, the entire set of custom elements needs to exist in a flat structure, including dependencies and stylesheets. Then, in the Angular HTML templates, you can import the custom elements by referencing the static asset location as follows: ```html <link rel="import" href="../../../../assets/oc-mt/src/app/polymerComponents/mt-img-suite/mt-img-suite.html"/> ``` Note the "`/assets/`” string in the href path above. TypeScript has a rule to identify this as a static dependency, which won’t be bundled by Webpack. Instead, the file will be served independently with the browser’s native approach to fetching dependencies. This means that all the assets will be available at runtime, but only the assets referenced in the code will actually be transferred to the client. # Internal Dependencies Within the Static Assets Directory Resolve Without Issue Just something to note... Within the custom elements, dependencies will be resolved using their relative path as long as the dependencies live within the flat static asset directory. Therefore, in this approach, there’s no need to modify any of the dependency import paths within the elements. # CUSTOM_ELEMENTS_SCHEMA in Module Definition By default, Angular will throw an error when using custom HTML elements. In order to use the browser’s built in custom web element mechanism and make Angular compliant to HTML5 recommendations, you need to tell Angular to expect custom elements. This can be accomplished in each module definition with the `CUSTOM_ELEMENTS_SCHEMA`. An example is as follows: ```javascript import { NgModule, CUSTOM_ELEMENTS_SCHEMA } from '@angular/core'; @NgModule({ schemas: [ CUSTOM_ELEMENTS_SCHEMA ], // Needed to use custom web elements imports: [], declarations: [ImgEditorComponent] }) export class ImgEditorModule { } ``` In the above example, the `CUSTOM_ELEMENTS_SCHEMA` definition is pulled out of the Angular package. It’s then added to the `schema` property in the module decoration object. In short, this simply tells Angular to ignore not having a factory definition for elements during template parsing and let the browser do its thing once the DOM is generated. # Multiple Dependency Instances Custom elements use the browser’s built in ability to determine when shared dependencies already exist and make previously fetched/installed dependencies available without reloading them. This is done by using each dependency’s absolute path. Since Angular-TypeScript projects use Webpack for dependency resolution, their location is lost during the transpile/build step and the browser’s built in method doesn’t work. Unfortunately, there’s no way for custom elements to know what global dependencies are unpacked and available without making the custom elements TypeScript components or building custom logic to check each dependency. The result is that custom elements using HTML5 specifications may define one instance of a dependency while the TypeScript components use a different instance. For example, the custom elements will all share the same version of jQuery if they import it from the same path in the flat, static asset directory structure. Meanwhile, Angular will have its own version defined in the global scope or a version scoped within individual views/modules/components. There isn’t really anything that needs to be done about this in most cases. It’s just something to be aware of since it could lead to issues that may be hard to identify. For example, if certain libraries within the custom elements attach themselves to jQuery (`$`), they probably won’t be available within Angular if you try to use them. They’ll need to be attached separately in Angular also and vice-versa. # Style Encapsulation When the Shadow DOM is used, it’s possible for custom elements to fully encapsulate their style class definitions so that only the child elements within them are affected. This allows global style definitions (themes) to be applied to custom elements without the risk of the custom elements’ internal style definitions affecting elements outside their scope. Unfortunately, Angular’s synthesized Shadow DOM approach of style encapsulation either fully encapsulates style classes or does not encapsulate them at all. By default, global style classes do not make it into custom elements and custom element style definitions do not affect elements outside their scope (module, view, etc.). I have not found a way to allow global style definitions (themes) into custom elements and, at the same time, encapsulate custom element style definitions from creeping out. Therefore, the workaround is to disable style encapsulation completely and refactor each element’s style classes and definitions to only impact child elements within the custom elements. This can be a tedious task, but it does enforce good practices. To disable style encapsulation completely in Angular, the `encapsulation: ViewEncapsulation.None` property can be added to the component decorator as follows: ```javascript import {Component, ViewEncapsulation} from '@angular/core'; @Component({ selector: 'mvi-img-editor', templateUrl: './img-editor.component.html', styleUrls: ['./img-editor.component.css'], encapsulation: ViewEncapsulation.None // Required to have styles applied to custom elements }) ``` The above property turns off the styling encapsulation completely making it possible (and likely) that styles will leak out of the custom elements and into other areas of the DOM. To fix this, each custom element’s style classes and definitions may need to be refactored to target more specific scopes. For example, if a custom element has a style definition for `div`, it may need to be refactored to only affect divs within the component as follows: ```css mt-img-suite div { ... } ``` # Angular Navigation Destroys and Re-Creates Views Typically, in a single page application, views are simply hidden and shown when navigating between them. Meanwhile, Angular’s built in routing completely destroys the views and recreates them when navigating. There are several issues with this approach that need to be accounted for. For example, any references in memory need to be recreated with each navigation. Additionally, event handlers attached to elements outside the scope of the custom element need to be meticulously managed. If the custom element attaches an event handler to the `document` or `body` of the DOM during initialization, the handlers will be attached over and over each time the view loads, causing them to be executed multiple times when the event they're attached to triggers. A simple solution to preventing multiple event handler executions is to simply remove an event listener before it's attached. For example, the following code removes a listener before attaching it: ```javascript document.removeEventListener('editorSuiteExportClicked', this.processExportedImage); document.addEventListener('editorSuiteExportClicked', this.processExportedImage); ``` In the above example, the first time this module loads, the `removeEventListener()` method will do nothing since the listener hasn’t been attached yet. The second time it loads, it will remove the previously attached listener so that the handler is only fired once for that event, regardless of how many times Angular initializes the same module when routing. Alternatively, a common approach in dealing with Angular’s built in, destructive routing is to use the [AngularUI UI-Router library](https://github.com/angular-ui/ui-router). Not only does the UI-Router have a non-destructive approach, it has several options that facilitate additional use cases, such as nested views and dynamic states. # Summary I’d like to say that this guide simply proves why Angular is a bad choice for any project. However, I’m sure you’ve been dictated to use Angular from a manager or boss who’s never created a web application and only wants you to use it because “everyone else is using it”. Regardless, after going through the trials and making a few tweaks, I believe custom elements fit extremely well in Angular projects without any functional limitations. Considering that several libraries need to be entirely re-written or re-factored to even come close to working in Angular, the above steps really aren’t that bad. Actually, I consider most of the above work to simply be project configuration and enforcement of best practices. Once configured, I’m sure you’ll find that there’s not much refactoring at all. Hopefully, this guide is enough to get you started with custom elements in an Angular 2, 3, 4, 5 (, 6?) project. If not, or if you find any additional hurdles, hoops or shortcuts, please let me know and I’ll add the info. Until then… may your product’s only limitation be imagination. |
| json metadata | {"tags":["angular","web","development","webcomponent","typescript"],"links":["https://www.w3.org/TR/custom-elements/","https://github.com/angular-ui/ui-router"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #19878200/Trx f490ec96cb7a008be9c88430ec497b277e29021b |
View Raw JSON Data
{
"trx_id": "f490ec96cb7a008be9c88430ec497b277e29021b",
"block": 19878200,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-15T01:43:57",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "angular",
"author": "a-diddy",
"permlink": "using-custom-elements-in-an-angular-typescript-project",
"title": "Using Custom Elements in an Angular TypeScript Project",
"body": "# Introduction\n\n\nCustom web elements are the future of web development. Their ease of use and modularization of HTML, CSS and JS make them perfect for sharing in multiple applications with as little work as possible. Importing a custom element into a project is as easy adding a CSS file. Then use them like any other HTML element, passing configuration and properties into them without the need to write any JS.\n\n````html\n<link rel=\"import\" href=\"../../../../assets/oc-mt/src/app/polymerComponents/mt-img-suite/mt-img-suite.html\"/>\n \n \n<mt-img-suite editor-id=\"editorSuite\"\n image-editor-config-url=\"../../../../assets/config/hiddenButtons-image-editor-config.json\"\n stylesheet=\"../../../../assets/css/img-editor-MVI.css\"\n mobile-controls=\"false\"\n edit-eyes=\"true\"\n></mt-img-suite>\n````\n\n\nCustom elements are not only a great way to encapsulate and share modularized functions and features, they’re also part of the [HTML5 specification](https://www.w3.org/TR/custom-elements/). That means they can be used in any web application that adheres to web standards. \n\nUnfortunately, some frameworks don’t fully play by the rules and need some tweaking to perform as one would expect. Among the worst offenders of all time is AngularJS. However, fortunately, custom elements are so powerful that even the Angular developers yielded to the custom element revolution and decided to embrace their usage. This was one of the main reasons Angular 2 was created. Basically, it was a near complete rewrite of the project to utilize more of the browser’s built in ability to manage custom elements, which is nearly 10 times more efficient than AngularJS's parsing approach.\n\nToday, Angular 2 plays along very nicely with custom elements. While Angular still comes with its own quirks, terminology and approaches, custom elements can be used in any Angular project without any limitations. \n\nThe below topics discuss the main hurdles I’ve come across while using custom elements in an Angular 5 project developed in TypeScript. While it may seem like a lot, I’m convinced that once these quirks are known and addressed, TypeScript, Angular and the custom elements can all play nicely without any limitations.\n\n\n \n# Static Assets\n\nTypeScript uses dynamic dependency injection during build/run time and, using Webpack, concatenates the dependencies into a series of bundles that are downloaded and executed in a certain order. This is a great approach for JS files and for HTML files, which get transferred as string data and parsed as needed. However, the parsing performed on the client does not appear to support HTML files that have JS `<script>` elements in them and vice-versa. The `<script>` content will be interpreted as a string when the HTML is injected in the DOM. \n\nThe workaround to this is to place custom HTML5 elements inside the static asset directory, “src/assets/”, with all of their dependencies. In summary, within the “assets” directory, the entire set of custom elements needs to exist in a flat structure, including dependencies and stylesheets. Then, in the Angular HTML templates, you can import the custom elements by referencing the static asset location as follows:\n\n```html\n<link rel=\"import\" href=\"../../../../assets/oc-mt/src/app/polymerComponents/mt-img-suite/mt-img-suite.html\"/>\n```\n\nNote the \"`/assets/`” string in the href path above. TypeScript has a rule to identify this as a static dependency, which won’t be bundled by Webpack. Instead, the file will be served independently with the browser’s native approach to fetching dependencies. This means that all the assets will be available at runtime, but only the assets referenced in the code will actually be transferred to the client.\n\n\n# Internal Dependencies Within the Static Assets Directory Resolve Without Issue\n\nJust something to note... \nWithin the custom elements, dependencies will be resolved using their relative path as long as the dependencies live within the flat static asset directory. Therefore, in this approach, there’s no need to modify any of the dependency import paths within the elements. \n\n\n \n# CUSTOM_ELEMENTS_SCHEMA in Module Definition\n\nBy default, Angular will throw an error when using custom HTML elements. In order to use the browser’s built in custom web element mechanism and make Angular compliant to HTML5 recommendations, you need to tell Angular to expect custom elements. This can be accomplished in each module definition with the `CUSTOM_ELEMENTS_SCHEMA`. An example is as follows:\n\n```javascript\nimport { NgModule, CUSTOM_ELEMENTS_SCHEMA } from '@angular/core';\n@NgModule({\n schemas: [ CUSTOM_ELEMENTS_SCHEMA ], // Needed to use custom web elements\n imports: [],\n declarations: [ImgEditorComponent]\n})\nexport class ImgEditorModule { }\n```\n\nIn the above example, the `CUSTOM_ELEMENTS_SCHEMA` definition is pulled out of the Angular package. It’s then added to the `schema` property in the module decoration object. In short, this simply tells Angular to ignore not having a factory definition for elements during template parsing and let the browser do its thing once the DOM is generated.\n\n\n# Multiple Dependency Instances\n\nCustom elements use the browser’s built in ability to determine when shared dependencies already exist and make previously fetched/installed dependencies available without reloading them. This is done by using each dependency’s absolute path. Since Angular-TypeScript projects use Webpack for dependency resolution, their location is lost during the transpile/build step and the browser’s built in method doesn’t work.\n\nUnfortunately, there’s no way for custom elements to know what global dependencies are unpacked and available without making the custom elements TypeScript components or building custom logic to check each dependency. The result is that custom elements using HTML5 specifications may define one instance of a dependency while the TypeScript components use a different instance. For example, the custom elements will all share the same version of jQuery if they import it from the same path in the flat, static asset directory structure. Meanwhile, Angular will have its own version defined in the global scope or a version scoped within individual views/modules/components.\n\nThere isn’t really anything that needs to be done about this in most cases. It’s just something to be aware of since it could lead to issues that may be hard to identify. For example, if certain libraries within the custom elements attach themselves to jQuery (`$`), they probably won’t be available within Angular if you try to use them. They’ll need to be attached separately in Angular also and vice-versa. \n\n\n# Style Encapsulation\n\nWhen the Shadow DOM is used, it’s possible for custom elements to fully encapsulate their style class definitions so that only the child elements within them are affected. This allows global style definitions (themes) to be applied to custom elements without the risk of the custom elements’ internal style definitions affecting elements outside their scope.\n\nUnfortunately, Angular’s synthesized Shadow DOM approach of style encapsulation either fully encapsulates style classes or does not encapsulate them at all. By default, global style classes do not make it into custom elements and custom element style definitions do not affect elements outside their scope (module, view, etc.). I have not found a way to allow global style definitions (themes) into custom elements and, at the same time, encapsulate custom element style definitions from creeping out. Therefore, the workaround is to disable style encapsulation completely and refactor each element’s style classes and definitions to only impact child elements within the custom elements. This can be a tedious task, but it does enforce good practices.\n\nTo disable style encapsulation completely in Angular, the `encapsulation: ViewEncapsulation.None` property can be added to the component decorator as follows: \n\n```javascript\nimport {Component, ViewEncapsulation} from '@angular/core';\n\n@Component({\n selector: 'mvi-img-editor',\n templateUrl: './img-editor.component.html',\n styleUrls: ['./img-editor.component.css'],\n encapsulation: ViewEncapsulation.None // Required to have styles applied to custom elements\n})\n```\n\n\nThe above property turns off the styling encapsulation completely making it possible (and likely) that styles will leak out of the custom elements and into other areas of the DOM. To fix this, each custom element’s style classes and definitions may need to be refactored to target more specific scopes. For example, if a custom element has a style definition for `div`, it may need to be refactored to only affect divs within the component as follows:\n\n```css\nmt-img-suite div {\n...\n}\n```\n \n# Angular Navigation Destroys and Re-Creates Views\n\nTypically, in a single page application, views are simply hidden and shown when navigating between them. Meanwhile, Angular’s built in routing completely destroys the views and recreates them when navigating. There are several issues with this approach that need to be accounted for. For example, any references in memory need to be recreated with each navigation. \n\nAdditionally, event handlers attached to elements outside the scope of the custom element need to be meticulously managed. If the custom element attaches an event handler to the `document` or `body` of the DOM during initialization, the handlers will be attached over and over each time the view loads, causing them to be executed multiple times when the event they're attached to triggers.\n\nA simple solution to preventing multiple event handler executions is to simply remove an event listener before it's attached. For example, the following code removes a listener before attaching it:\n\n```javascript\ndocument.removeEventListener('editorSuiteExportClicked', this.processExportedImage);\ndocument.addEventListener('editorSuiteExportClicked', this.processExportedImage);\n```\n\nIn the above example, the first time this module loads, the `removeEventListener()` method will do nothing since the listener hasn’t been attached yet. The second time it loads, it will remove the previously attached listener so that the handler is only fired once for that event, regardless of how many times Angular initializes the same module when routing.\n\nAlternatively, a common approach in dealing with Angular’s built in, destructive routing is to use the [AngularUI UI-Router library](https://github.com/angular-ui/ui-router). Not only does the UI-Router have a non-destructive approach, it has several options that facilitate additional use cases, such as nested views and dynamic states.\n\n\n# Summary\n\nI’d like to say that this guide simply proves why Angular is a bad choice for any project. However, I’m sure you’ve been dictated to use Angular from a manager or boss who’s never created a web application and only wants you to use it because “everyone else is using it”. Regardless, after going through the trials and making a few tweaks, I believe custom elements fit extremely well in Angular projects without any functional limitations. \n\nConsidering that several libraries need to be entirely re-written or re-factored to even come close to working in Angular, the above steps really aren’t that bad. Actually, I consider most of the above work to simply be project configuration and enforcement of best practices. Once configured, I’m sure you’ll find that there’s not much refactoring at all.\n\nHopefully, this guide is enough to get you started with custom elements in an Angular 2, 3, 4, 5 (, 6?) project. If not, or if you find any additional hurdles, hoops or shortcuts, please let me know and I’ll add the info. Until then… may your product’s only limitation be imagination.",
"json_metadata": "{\"tags\":[\"angular\",\"web\",\"development\",\"webcomponent\",\"typescript\"],\"links\":[\"https://www.w3.org/TR/custom-elements/\",\"https://github.com/angular-ui/ui-router\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}a-diddyupvoted (100.00%) @chronicusprime / how-to-try-out-lightning-network-using-eclair-app-for-android2018/01/19 15:36:18
a-diddyupvoted (100.00%) @chronicusprime / how-to-try-out-lightning-network-using-eclair-app-for-android
2018/01/19 15:36:18
| voter | a-diddy |
| author | chronicusprime |
| permlink | how-to-try-out-lightning-network-using-eclair-app-for-android |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19118126/Trx f7bb063658c45138ecdfc8edabcfd719a3f999fc |
View Raw JSON Data
{
"trx_id": "f7bb063658c45138ecdfc8edabcfd719a3f999fc",
"block": 19118126,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-19T15:36:18",
"op": [
"vote",
{
"voter": "a-diddy",
"author": "chronicusprime",
"permlink": "how-to-try-out-lightning-network-using-eclair-app-for-android",
"weight": 10000
}
]
}money-dreamersent 0.001 STEEM to @a-diddy- "I just followed you!"2018/01/11 04:20:15
money-dreamersent 0.001 STEEM to @a-diddy- "I just followed you!"
2018/01/11 04:20:15
| from | money-dreamer |
| to | a-diddy |
| amount | 0.001 STEEM |
| memo | I just followed you! |
| Transaction Info | Block #18874379/Trx 21d0b693108d4bc97e5cc3768ac824ca6955f144 |
View Raw JSON Data
{
"trx_id": "21d0b693108d4bc97e5cc3768ac824ca6955f144",
"block": 18874379,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-11T04:20:15",
"op": [
"transfer",
{
"from": "money-dreamer",
"to": "a-diddy",
"amount": "0.001 STEEM",
"memo": "I just followed you!"
}
]
}2018/01/03 16:48:00
2018/01/03 16:48:00
| required auths | [] |
| required posting auths | ["a-diddy"] |
| id | follow |
| json | ["follow",{"follower":"a-diddy","following":"haejin","what":["blog"]}] |
| Transaction Info | Block #18659097/Trx a46c487c83b4e67641fdf5a60ae579a22b3441a0 |
View Raw JSON Data
{
"trx_id": "a46c487c83b4e67641fdf5a60ae579a22b3441a0",
"block": 18659097,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-03T16:48:00",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"a-diddy"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"a-diddy\",\"following\":\"haejin\",\"what\":[\"blog\"]}]"
}
]
}a-diddyupvoted (100.00%) @bad.r2017 / how-to-create-a-paper-wallet-for-any-cryptocurrency-in-7-steps2017/12/13 20:05:54
a-diddyupvoted (100.00%) @bad.r2017 / how-to-create-a-paper-wallet-for-any-cryptocurrency-in-7-steps
2017/12/13 20:05:54
| voter | a-diddy |
| author | bad.r2017 |
| permlink | how-to-create-a-paper-wallet-for-any-cryptocurrency-in-7-steps |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18058680/Trx aa6f6cbd19ea27e503276f50ff8742b9637497aa |
View Raw JSON Data
{
"trx_id": "aa6f6cbd19ea27e503276f50ff8742b9637497aa",
"block": 18058680,
"trx_in_block": 32,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-13T20:05:54",
"op": [
"vote",
{
"voter": "a-diddy",
"author": "bad.r2017",
"permlink": "how-to-create-a-paper-wallet-for-any-cryptocurrency-in-7-steps",
"weight": 10000
}
]
}2017/12/12 22:23:33
2017/12/12 22:23:33
| delegator | steem |
| delegatee | a-diddy |
| vesting shares | 29737.273070 VESTS |
| Transaction Info | Block #18032654/Trx 22dcceafcfd2a90e0eee740a090795baa8c33bfe |
View Raw JSON Data
{
"trx_id": "22dcceafcfd2a90e0eee740a090795baa8c33bfe",
"block": 18032654,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-12T22:23:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "a-diddy",
"vesting_shares": "29737.273070 VESTS"
}
]
}a-diddyupvoted (100.00%) @senatorbrakey / introducing-the-first-steem-powered-us-senate-campaign2017/10/13 16:52:18
a-diddyupvoted (100.00%) @senatorbrakey / introducing-the-first-steem-powered-us-senate-campaign
2017/10/13 16:52:18
| voter | a-diddy |
| author | senatorbrakey |
| permlink | introducing-the-first-steem-powered-us-senate-campaign |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16299228/Trx e4e16188bb25551cf5bf1fdf187d9de705802713 |
View Raw JSON Data
{
"trx_id": "e4e16188bb25551cf5bf1fdf187d9de705802713",
"block": 16299228,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-13T16:52:18",
"op": [
"vote",
{
"voter": "a-diddy",
"author": "senatorbrakey",
"permlink": "introducing-the-first-steem-powered-us-senate-campaign",
"weight": 10000
}
]
}a-diddyupvoted (100.00%) @thecryptofiend / the-missing-faq-a-beginners-guide-to-using-steemit2017/10/13 16:46:42
a-diddyupvoted (100.00%) @thecryptofiend / the-missing-faq-a-beginners-guide-to-using-steemit
2017/10/13 16:46:42
| voter | a-diddy |
| author | thecryptofiend |
| permlink | the-missing-faq-a-beginners-guide-to-using-steemit |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16299116/Trx 81731c8d7c550bde5031fa6dd2eecdb1e912f04f |
View Raw JSON Data
{
"trx_id": "81731c8d7c550bde5031fa6dd2eecdb1e912f04f",
"block": 16299116,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-13T16:46:42",
"op": [
"vote",
{
"voter": "a-diddy",
"author": "thecryptofiend",
"permlink": "the-missing-faq-a-beginners-guide-to-using-steemit",
"weight": 10000
}
]
}a-diddyupdated their account properties2017/10/13 16:36:18
a-diddyupdated their account properties
2017/10/13 16:36:18
| account | a-diddy |
| memo key | STM8cgFdqKxoCZVNuPQZxShW6DMLYQ459N3KTWNdnx8jFutEAQqUx |
| json metadata | {"profile":{"profile_image":"https://pbs.twimg.com/profile_images/852573150155907072/hPoWclvw_400x400.jpg","cover_image":"https://pbs.twimg.com/profile_banners/20545714/1492104252/1500x500","name":"Austin [NO2X]","about":"Software, EE, Crypto, Snowboarding, Photography, Alchemy and Ascension","location":"Orange County, CA"}} |
| Transaction Info | Block #16298908/Trx 1c6e480019cf12a940699b5f2e828c4be733eed7 |
View Raw JSON Data
{
"trx_id": "1c6e480019cf12a940699b5f2e828c4be733eed7",
"block": 16298908,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-13T16:36:18",
"op": [
"account_update",
{
"account": "a-diddy",
"memo_key": "STM8cgFdqKxoCZVNuPQZxShW6DMLYQ459N3KTWNdnx8jFutEAQqUx",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/852573150155907072/hPoWclvw_400x400.jpg\",\"cover_image\":\"https://pbs.twimg.com/profile_banners/20545714/1492104252/1500x500\",\"name\":\"Austin [NO2X]\",\"about\":\"Software, EE, Crypto, Snowboarding, Photography, Alchemy and Ascension\",\"location\":\"Orange County, CA\"}}"
}
]
}2017/10/13 16:31:39
2017/10/13 16:31:39
| fee | 0.500 STEEM |
| delegation | 57000.000000 VESTS |
| creator | steem |
| new account name | a-diddy |
| owner | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM7sgRawejtQzm1zF9wcMv4MGBSRDddWR7CAd5QG9PsQ9vy8JL7m",1]]} |
| active | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM7KWhqYeFXNAG7srPtDAxJG2mJMzUL3n1HEHrTjr8y57nUwPHVJ",1]]} |
| posting | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM5uc2PotR6PKVP9x1ZS2i5th4561C6tqnpmPXahKwrf4jU9XcQL",1]]} |
| memo key | STM8cgFdqKxoCZVNuPQZxShW6DMLYQ459N3KTWNdnx8jFutEAQqUx |
| json metadata | |
| extensions | [] |
| Transaction Info | Block #16298815/Trx ddde1e61b837cff18439528d16eaaba193b67521 |
View Raw JSON Data
{
"trx_id": "ddde1e61b837cff18439528d16eaaba193b67521",
"block": 16298815,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-13T16:31:39",
"op": [
"account_create_with_delegation",
{
"fee": "0.500 STEEM",
"delegation": "57000.000000 VESTS",
"creator": "steem",
"new_account_name": "a-diddy",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7sgRawejtQzm1zF9wcMv4MGBSRDddWR7CAd5QG9PsQ9vy8JL7m",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7KWhqYeFXNAG7srPtDAxJG2mJMzUL3n1HEHrTjr8y57nUwPHVJ",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5uc2PotR6PKVP9x1ZS2i5th4561C6tqnpmPXahKwrf4jU9XcQL",
1
]
]
},
"memo_key": "STM8cgFdqKxoCZVNuPQZxShW6DMLYQ459N3KTWNdnx8jFutEAQqUx",
"json_metadata": "",
"extensions": []
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779050721
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779050721
},
"rc_account": {
"account": "a-diddy",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779050721
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"https://pbs.twimg.com/profile_images/852573150155907072/hPoWclvw_400x400.jpg","cover_image":"https://pbs.twimg.com/profile_banners/20545714/1492104252/1500x500","name":"Austin [NO2X]","about":"Software, EE, Crypto, Snowboarding, Photography, Alchemy and Ascension","location":"Orange County, CA"} |
| JSON METADATA | |
| profile | {"profile_image":"https://pbs.twimg.com/profile_images/852573150155907072/hPoWclvw_400x400.jpg","cover_image":"https://pbs.twimg.com/profile_banners/20545714/1492104252/1500x500","name":"Austin [NO2X]","about":"Software, EE, Crypto, Snowboarding, Photography, Alchemy and Ascension","location":"Orange County, CA"} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "https://pbs.twimg.com/profile_images/852573150155907072/hPoWclvw_400x400.jpg",
"cover_image": "https://pbs.twimg.com/profile_banners/20545714/1492104252/1500x500",
"name": "Austin [NO2X]",
"about": "Software, EE, Crypto, Snowboarding, Photography, Alchemy and Ascension",
"location": "Orange County, CA"
}
},
"json_metadata": {
"profile": {
"profile_image": "https://pbs.twimg.com/profile_images/852573150155907072/hPoWclvw_400x400.jpg",
"cover_image": "https://pbs.twimg.com/profile_banners/20545714/1492104252/1500x500",
"name": "Austin [NO2X]",
"about": "Software, EE, Crypto, Snowboarding, Photography, Alchemy and Ascension",
"location": "Orange County, CA"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM7sgRawejtQzm1zF9wcMv4MGBSRDddWR7CAd5QG9PsQ9vy8JL7m1/1
Active
Single Signature
Public Keys
STM7KWhqYeFXNAG7srPtDAxJG2mJMzUL3n1HEHrTjr8y57nUwPHVJ1/1
Posting
Single Signature
Public Keys
STM5uc2PotR6PKVP9x1ZS2i5th4561C6tqnpmPXahKwrf4jU9XcQL1/1
Memo
STM8cgFdqKxoCZVNuPQZxShW6DMLYQ459N3KTWNdnx8jFutEAQqUx
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7sgRawejtQzm1zF9wcMv4MGBSRDddWR7CAd5QG9PsQ9vy8JL7m",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7KWhqYeFXNAG7srPtDAxJG2mJMzUL3n1HEHrTjr8y57nUwPHVJ",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5uc2PotR6PKVP9x1ZS2i5th4561C6tqnpmPXahKwrf4jU9XcQL",
1
]
]
},
"memo": "STM8cgFdqKxoCZVNuPQZxShW6DMLYQ459N3KTWNdnx8jFutEAQqUx"
}Witness Votes
0 / 30
No active witness votes.
[]