Ecoer Logo
VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.037USD
STEEM
0.002STEEM
SBD
0.000SBD
Effective Power
5.007SP
├── Own SP
0.629SP
└── Incoming Deleg
+4.378SP

Detailed Balance

STEEM
balance
0.002STEEM
market_balance
0.000STEEM
savings_balance
0.000STEEM
reward_steem_balance
0.000STEEM
STEEM POWER
Own SP
0.629SP
Delegated Out
0.000SP
Delegation In
4.378SP
Effective Power
5.007SP
Reward SP (pending)
0.000SP
SBD
sbd_balance
0.000SBD
sbd_conversions
0.000SBD
sbd_market_balance
0.000SBD
savings_sbd_balance
0.000SBD
reward_sbd_balance
0.000SBD
{
  "balance": "0.002 STEEM",
  "savings_balance": "0.000 STEEM",
  "reward_steem_balance": "0.000 STEEM",
  "vesting_shares": "1022.774121 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "7120.885685 VESTS",
  "sbd_balance": "0.000 SBD",
  "savings_sbd_balance": "0.000 SBD",
  "reward_sbd_balance": "0.000 SBD",
  "conversions": []
}

Account Info

namemikethemechanic
id721853
rank1,427,782
reputation2581982
created2018-02-05T14:06:09
recovery_accountsteem
proxyNone
post_count1
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2018-03-01T09:26:24
last_root_post2018-03-01T09:26:24
last_vote_time2018-03-06T15:00:18
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power0
delayed_votes0
balance0.002 STEEM
savings_balance0.000 STEEM
sbd_balance0.000 SBD
savings_sbd_balance0.000 SBD
vesting_shares1022.774121 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares7120.885685 VESTS
reward_vesting_balance0.000000 VESTS
vesting_balance0.000 STEEM
vesting_withdraw_rate0.000000 VESTS
next_vesting_withdrawal1969-12-31T23:59:59
withdrawn0
to_withdraw0
withdraw_routes0
savings_withdraw_requests0
last_account_recovery1970-01-01T00:00:00
reset_accountnull
last_owner_update1970-01-01T00:00:00
last_account_update2020-12-22T09:21:45
minedNo
sbd_seconds0
sbd_last_interest_payment1970-01-01T00:00:00
savings_sbd_last_interest_payment1970-01-01T00:00:00
{
  "active": {
    "account_auths": [],
    "key_auths": [
      [
        "STM8DLbm7LdQo4SBQYQWvqRTtBTfkTW8qrQTQXBjRV2Vcf6CojYz7",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "balance": "0.002 STEEM",
  "can_vote": true,
  "comment_count": 0,
  "created": "2018-02-05T14:06:09",
  "curation_rewards": 0,
  "delegated_vesting_shares": "0.000000 VESTS",
  "downvote_manabar": {
    "current_mana": 2035914951,
    "last_update_time": 1779076065
  },
  "guest_bloggers": [],
  "id": 721853,
  "json_metadata": "{\"profile\":{\"name\":\"MikeTheMechanic\",\"location\":\"Germany\",\"profile_image\":\"https://s10.postimg.org/7dc9wx2uh/klein.jpg\"}}",
  "last_account_recovery": "1970-01-01T00:00:00",
  "last_account_update": "2020-12-22T09:21:45",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_post": "2018-03-01T09:26:24",
  "last_root_post": "2018-03-01T09:26:24",
  "last_vote_time": "2018-03-06T15:00:18",
  "lifetime_vote_count": 0,
  "market_history": [],
  "memo_key": "STM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv",
  "mined": false,
  "name": "mikethemechanic",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "other_history": [],
  "owner": {
    "account_auths": [],
    "key_auths": [
      [
        "STM78BKfUMdUMEWNUnQEqfW4oowYPB97HoNkFpTXeeYbgW6w5EdBN",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "pending_claimed_accounts": 0,
  "post_bandwidth": 0,
  "post_count": 1,
  "post_history": [],
  "posting": {
    "account_auths": [],
    "key_auths": [
      [
        "STM6ysoVQwqSsarinZQv3x3rjKMDCNP7o5xXo7ZQoEPjA1N4oo6VT",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "posting_json_metadata": "{\"profile\":{\"name\":\"MikeTheMechanic\",\"location\":\"Germany\",\"profile_image\":\"https://i.postimg.cc/K8hgSdLJ/Bild1.png\",\"cover_image\":\"https://i.postimg.cc/K8hgSdLJ/Bild1.png\",\"version\":2}}",
  "posting_rewards": 0,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "proxy": "",
  "received_vesting_shares": "7120.885685 VESTS",
  "recovery_account": "steem",
  "reputation": 2581982,
  "reset_account": "null",
  "reward_sbd_balance": "0.000 SBD",
  "reward_steem_balance": "0.000 STEEM",
  "reward_vesting_balance": "0.000000 VESTS",
  "reward_vesting_steem": "0.000 STEEM",
  "savings_balance": "0.000 STEEM",
  "savings_sbd_balance": "0.000 SBD",
  "savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_sbd_seconds": "0",
  "savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
  "savings_withdraw_requests": 0,
  "sbd_balance": "0.000 SBD",
  "sbd_last_interest_payment": "1970-01-01T00:00:00",
  "sbd_seconds": "0",
  "sbd_seconds_last_update": "1970-01-01T00:00:00",
  "tags_usage": [],
  "to_withdraw": 0,
  "transfer_history": [],
  "vesting_balance": "0.000 STEEM",
  "vesting_shares": "1022.774121 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "vote_history": [],
  "voting_manabar": {
    "current_mana": "8143659806",
    "last_update_time": 1779076065
  },
  "voting_power": 0,
  "withdraw_routes": 0,
  "withdrawn": 0,
  "witness_votes": [],
  "witnesses_voted_for": 0,
  "rank": 1427782
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
steemdelegated 4.378 SP to @mikethemechanic
2026/05/18 03:47:45
delegateemikethemechanic
delegatorsteem
vesting shares7120.885685 VESTS
Transaction InfoBlock #106147678/Trx 1c5c387d47cc6622a98b049e0236bcd9b8f426fb
View Raw JSON Data
{
  "block": 106147678,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "7120.885685 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-05-18T03:47:45",
  "trx_id": "1c5c387d47cc6622a98b049e0236bcd9b8f426fb",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 2.710 SP to @mikethemechanic
2026/05/12 18:11:24
delegateemikethemechanic
delegatorsteem
vesting shares4408.675280 VESTS
Transaction InfoBlock #105992892/Trx dfab4e274e10a84775cb212831aff15e1159c6f7
View Raw JSON Data
{
  "block": 105992892,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "4408.675280 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-05-12T18:11:24",
  "trx_id": "dfab4e274e10a84775cb212831aff15e1159c6f7",
  "trx_in_block": 1,
  "virtual_op": 0
}
steemdelegated 4.386 SP to @mikethemechanic
2026/04/26 03:03:06
delegateemikethemechanic
delegatorsteem
vesting shares7133.401441 VESTS
Transaction InfoBlock #105515230/Trx efef42f65df8a09e06e7252b72eb138c265bc93d
View Raw JSON Data
{
  "block": 105515230,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "7133.401441 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-04-26T03:03:06",
  "trx_id": "efef42f65df8a09e06e7252b72eb138c265bc93d",
  "trx_in_block": 1,
  "virtual_op": 0
}
steemdelegated 2.736 SP to @mikethemechanic
2026/01/23 17:18:21
delegateemikethemechanic
delegatorsteem
vesting shares4450.222099 VESTS
Transaction InfoBlock #102863200/Trx 7bd1a0441b9f9ba7694ff7f9ff9793cec326eda5
View Raw JSON Data
{
  "block": 102863200,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "4450.222099 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-01-23T17:18:21",
  "trx_id": "7bd1a0441b9f9ba7694ff7f9ff9793cec326eda5",
  "trx_in_block": 1,
  "virtual_op": 0
}
steemdelegated 2.837 SP to @mikethemechanic
2024/12/17 12:31:09
delegateemikethemechanic
delegatorsteem
vesting shares4614.441296 VESTS
Transaction InfoBlock #91309468/Trx 4b5cfed9cd747362492bddde26934ac8961f2fb4
View Raw JSON Data
{
  "block": 91309468,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "4614.441296 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2024-12-17T12:31:09",
  "trx_id": "4b5cfed9cd747362492bddde26934ac8961f2fb4",
  "trx_in_block": 2,
  "virtual_op": 0
}
steemdelegated 2.941 SP to @mikethemechanic
2023/11/14 04:12:57
delegateemikethemechanic
delegatorsteem
vesting shares4783.574828 VESTS
Transaction InfoBlock #79863642/Trx 65b04d651696536de75c3eaa1e387b76564c335b
View Raw JSON Data
{
  "block": 79863642,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "4783.574828 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2023-11-14T04:12:57",
  "trx_id": "65b04d651696536de75c3eaa1e387b76564c335b",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 4.747 SP to @mikethemechanic
2023/09/22 01:59:42
delegateemikethemechanic
delegatorsteem
vesting shares7720.853614 VESTS
Transaction InfoBlock #78352814/Trx 666c9ae02774e4da72648dbbea702aa3c28fecc4
View Raw JSON Data
{
  "block": 78352814,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "7720.853614 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2023-09-22T01:59:42",
  "trx_id": "666c9ae02774e4da72648dbbea702aa3c28fecc4",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 4.883 SP to @mikethemechanic
2022/11/03 15:16:51
delegateemikethemechanic
delegatorsteem
vesting shares7942.535052 VESTS
Transaction InfoBlock #69117533/Trx 47a8002b37ef61c94e625570777c2a914e1b2392
View Raw JSON Data
{
  "block": 69117533,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "7942.535052 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2022-11-03T15:16:51",
  "trx_id": "47a8002b37ef61c94e625570777c2a914e1b2392",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 5.018 SP to @mikethemechanic
2022/01/17 20:43:30
delegateemikethemechanic
delegatorsteem
vesting shares8162.642653 VESTS
Transaction InfoBlock #60821075/Trx 8ac2fb552871ccc451349b900d32719383a08ad7
View Raw JSON Data
{
  "block": 60821075,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "8162.642653 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2022-01-17T20:43:30",
  "trx_id": "8ac2fb552871ccc451349b900d32719383a08ad7",
  "trx_in_block": 2,
  "virtual_op": 0
}
steemdelegated 5.132 SP to @mikethemechanic
2021/06/14 04:00:48
delegateemikethemechanic
delegatorsteem
vesting shares8346.836941 VESTS
Transaction InfoBlock #54611538/Trx 8d87705c3990cc912fa3d61588fce77571abc061
View Raw JSON Data
{
  "block": 54611538,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "8346.836941 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2021-06-14T04:00:48",
  "trx_id": "8d87705c3990cc912fa3d61588fce77571abc061",
  "trx_in_block": 1,
  "virtual_op": 0
}
mikethemechanicupdated their account properties
2020/12/22 09:21:45
accountmikethemechanic
extensions[]
json metadata
posting json metadata{"profile":{"name":"MikeTheMechanic","location":"Germany","profile_image":"https://i.postimg.cc/K8hgSdLJ/Bild1.png","cover_image":"https://i.postimg.cc/K8hgSdLJ/Bild1.png","version":2}}
Transaction InfoBlock #49664929/Trx 86014f6a26f7c66a968fdbd134d2ed8ce472a98b
View Raw JSON Data
{
  "block": 49664929,
  "op": [
    "account_update2",
    {
      "account": "mikethemechanic",
      "extensions": [],
      "json_metadata": "",
      "posting_json_metadata": "{\"profile\":{\"name\":\"MikeTheMechanic\",\"location\":\"Germany\",\"profile_image\":\"https://i.postimg.cc/K8hgSdLJ/Bild1.png\",\"cover_image\":\"https://i.postimg.cc/K8hgSdLJ/Bild1.png\",\"version\":2}}"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-22T09:21:45",
  "trx_id": "86014f6a26f7c66a968fdbd134d2ed8ce472a98b",
  "trx_in_block": 1,
  "virtual_op": 0
}
mikethemechanicupdated their account properties
2020/12/22 09:21:36
accountmikethemechanic
extensions[]
json metadata
posting json metadata{"profile":{"name":"MikeTheMechanic","location":"Germany","profile_image":"https://s10.postimg.org/7dc9wx2uh/klein.jpg","cover_image":"https://i.postimg.cc/K8hgSdLJ/Bild1.png","version":2}}
Transaction InfoBlock #49664926/Trx 169a6c000e72c8f59ca91f8e6989ac7ece43f1df
View Raw JSON Data
{
  "block": 49664926,
  "op": [
    "account_update2",
    {
      "account": "mikethemechanic",
      "extensions": [],
      "json_metadata": "",
      "posting_json_metadata": "{\"profile\":{\"name\":\"MikeTheMechanic\",\"location\":\"Germany\",\"profile_image\":\"https://s10.postimg.org/7dc9wx2uh/klein.jpg\",\"cover_image\":\"https://i.postimg.cc/K8hgSdLJ/Bild1.png\",\"version\":2}}"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-22T09:21:36",
  "trx_id": "169a6c000e72c8f59ca91f8e6989ac7ece43f1df",
  "trx_in_block": 6,
  "virtual_op": 0
}
mikethemechanicupdated their account properties
2020/12/22 09:21:03
accountmikethemechanic
extensions[]
json metadata
posting json metadata{"profile":{"name":"MikeTheMechanic","location":"Germany","profile_image":"https://cdn.steemitimages.com/DQmQctuq7DZnkhQotMKnTXPdx1Ab6BJyqv4FNkCCzqjWPSQ/Bild1.png","version":2}}
Transaction InfoBlock #49664915/Trx beebb84f07885e1a35e2b89b4e5c97edf4ff705c
View Raw JSON Data
{
  "block": 49664915,
  "op": [
    "account_update2",
    {
      "account": "mikethemechanic",
      "extensions": [],
      "json_metadata": "",
      "posting_json_metadata": "{\"profile\":{\"name\":\"MikeTheMechanic\",\"location\":\"Germany\",\"profile_image\":\"https://cdn.steemitimages.com/DQmQctuq7DZnkhQotMKnTXPdx1Ab6BJyqv4FNkCCzqjWPSQ/Bild1.png\",\"version\":2}}"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-22T09:21:03",
  "trx_id": "beebb84f07885e1a35e2b89b4e5c97edf4ff705c",
  "trx_in_block": 2,
  "virtual_op": 0
}
mikethemechanicupdated their account properties
2020/12/22 09:20:33
accountmikethemechanic
extensions[]
json metadata
posting json metadata{"profile":{"name":"MikeTheMechanic","location":"Germany","profile_image":"https://i.postimg.cc/K8hgSdLJ/Bild1.png","version":2}}
Transaction InfoBlock #49664905/Trx 617b95cae3145ae0e15080489bb7c0b7d1a1d186
View Raw JSON Data
{
  "block": 49664905,
  "op": [
    "account_update2",
    {
      "account": "mikethemechanic",
      "extensions": [],
      "json_metadata": "",
      "posting_json_metadata": "{\"profile\":{\"name\":\"MikeTheMechanic\",\"location\":\"Germany\",\"profile_image\":\"https://i.postimg.cc/K8hgSdLJ/Bild1.png\",\"version\":2}}"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-22T09:20:33",
  "trx_id": "617b95cae3145ae0e15080489bb7c0b7d1a1d186",
  "trx_in_block": 3,
  "virtual_op": 0
}
executive-boardsent 0.001 STEEM to @mikethemechanic- "❗ Hello mikethemechanic, great that you are using the STEEM blockchain. The Executive Board hereby invites you to https://discord.gg/KyBbmhh where you will get some insider infos on how you will earn ..."
2020/12/22 08:59:06
amount0.001 STEEM
fromexecutive-board
memo❗ Hello mikethemechanic, great that you are using the STEEM blockchain. The Executive Board hereby invites you to https://discord.gg/KyBbmhh where you will get some insider infos on how you will earn the most coins. It's easy, just follow the instructions. Warm regards, The Executive Board.
tomikethemechanic
Transaction InfoBlock #49664480/Trx 5a1a5cf957fc9423a821ddd51cc2908f06ac4f31
View Raw JSON Data
{
  "block": 49664480,
  "op": [
    "transfer",
    {
      "amount": "0.001 STEEM",
      "from": "executive-board",
      "memo": "❗ Hello mikethemechanic, great that you are using the STEEM blockchain. The Executive Board hereby invites you to https://discord.gg/KyBbmhh where you will get some insider infos on how you will earn the most coins. It's easy, just follow the instructions. Warm regards, The Executive Board.",
      "to": "mikethemechanic"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-22T08:59:06",
  "trx_id": "5a1a5cf957fc9423a821ddd51cc2908f06ac4f31",
  "trx_in_block": 0,
  "virtual_op": 0
}
beemenginesent 0.001 STEEM to @mikethemechanic- "🚀 Promoting Your Posts 24/24. Community Curation & Support. Checkout http://beemengine.live"
2020/12/22 08:58:42
amount0.001 STEEM
frombeemengine
memo🚀 Promoting Your Posts 24/24. Community Curation & Support. Checkout http://beemengine.live
tomikethemechanic
Transaction InfoBlock #49664472/Trx 8468784d124b264267567cec41c0c78414d7de63
View Raw JSON Data
{
  "block": 49664472,
  "op": [
    "transfer",
    {
      "amount": "0.001 STEEM",
      "from": "beemengine",
      "memo": "🚀 Promoting Your Posts 24/24. Community Curation & Support. Checkout http://beemengine.live",
      "to": "mikethemechanic"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-22T08:58:42",
  "trx_id": "8468784d124b264267567cec41c0c78414d7de63",
  "trx_in_block": 4,
  "virtual_op": 0
}
2020/12/22 08:57:42
authormikethemechanic
bodyttt
json metadata{"app":"steemit/0.2","format":"markdown","tags":["t"]}
parent author
parent permlinkblockchain
permlinkblockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics
titlet
Transaction InfoBlock #49664453/Trx 0be5de41023b4abdedd08dc3839bb971a190759f
View Raw JSON Data
{
  "block": 49664453,
  "op": [
    "comment",
    {
      "author": "mikethemechanic",
      "body": "ttt",
      "json_metadata": "{\"app\":\"steemit/0.2\",\"format\":\"markdown\",\"tags\":[\"t\"]}",
      "parent_author": "",
      "parent_permlink": "blockchain",
      "permlink": "blockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics",
      "title": "t"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-22T08:57:42",
  "trx_id": "0be5de41023b4abdedd08dc3839bb971a190759f",
  "trx_in_block": 8,
  "virtual_op": 0
}
steemdelegated 5.247 SP to @mikethemechanic
2020/12/11 14:15:33
delegateemikethemechanic
delegatorsteem
vesting shares8534.258915 VESTS
Transaction InfoBlock #49358875/Trx 3a4aa1bce1cd184524148477dc85ba1d9b8beef3
View Raw JSON Data
{
  "block": 49358875,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "8534.258915 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-11T14:15:33",
  "trx_id": "3a4aa1bce1cd184524148477dc85ba1d9b8beef3",
  "trx_in_block": 1,
  "virtual_op": 0
}
steemdelegated 1.176 SP to @mikethemechanic
2020/12/06 07:51:36
delegateemikethemechanic
delegatorsteem
vesting shares1912.543513 VESTS
Transaction InfoBlock #49210408/Trx 5bc9b28e7784fbc94cb768ae9a5011e08237c0e4
View Raw JSON Data
{
  "block": 49210408,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "1912.543513 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-06T07:51:36",
  "trx_id": "5bc9b28e7784fbc94cb768ae9a5011e08237c0e4",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 5.251 SP to @mikethemechanic
2020/12/05 17:53:21
delegateemikethemechanic
delegatorsteem
vesting shares8540.466769 VESTS
Transaction InfoBlock #49193961/Trx f3e5b7047da9526f18381946bca71fb65e1b084f
View Raw JSON Data
{
  "block": 49193961,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "8540.466769 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-05T17:53:21",
  "trx_id": "f3e5b7047da9526f18381946bca71fb65e1b084f",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 1.180 SP to @mikethemechanic
2020/11/02 22:08:30
delegateemikethemechanic
delegatorsteem
vesting shares1920.017158 VESTS
Transaction InfoBlock #48265461/Trx 7d32868d6f91e6d556548ed43efac31c33bfbad8
View Raw JSON Data
{
  "block": 48265461,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "1920.017158 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-11-02T22:08:30",
  "trx_id": "7d32868d6f91e6d556548ed43efac31c33bfbad8",
  "trx_in_block": 3,
  "virtual_op": 0
}
steemdelegated 5.375 SP to @mikethemechanic
2020/05/09 08:52:30
delegateemikethemechanic
delegatorsteem
vesting shares8743.272128 VESTS
Transaction InfoBlock #43220708/Trx 5a5739b932cf2f7fcfec7960bfc04ac484eba3dc
View Raw JSON Data
{
  "block": 43220708,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "8743.272128 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-05-09T08:52:30",
  "trx_id": "5a5739b932cf2f7fcfec7960bfc04ac484eba3dc",
  "trx_in_block": 25,
  "virtual_op": 0
}
steemdelegated 1.201 SP to @mikethemechanic
2020/05/08 12:57:12
delegateemikethemechanic
delegatorsteem
vesting shares1953.311140 VESTS
Transaction InfoBlock #43197365/Trx 3e8b3d1b2bd5eb5c017b4698debe9b5d2895dabf
View Raw JSON Data
{
  "block": 43197365,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "1953.311140 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-05-08T12:57:12",
  "trx_id": "3e8b3d1b2bd5eb5c017b4698debe9b5d2895dabf",
  "trx_in_block": 21,
  "virtual_op": 0
}
steemdelegated 5.377 SP to @mikethemechanic
2020/05/04 03:21:09
delegateemikethemechanic
delegatorsteem
vesting shares8746.166139 VESTS
Transaction InfoBlock #43073695/Trx 8640ddd085c0f9da7172949aadb7b9b7d29c9340
View Raw JSON Data
{
  "block": 43073695,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "8746.166139 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-05-04T03:21:09",
  "trx_id": "8640ddd085c0f9da7172949aadb7b9b7d29c9340",
  "trx_in_block": 0,
  "virtual_op": 0
}
2020/02/05 16:25:33
authorsteemitboard
bodyCongratulations @mikethemechanic! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@mikethemechanic/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/@mikethemechanic) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=mikethemechanic)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-a-better-rich-list-comparator"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-a-better-rich-list-comparator">SteemitBoard Ranking update - A better rich list comparator</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"]}
parent authormikethemechanic
parent permlinkblockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics
permlinksteemitboard-notify-mikethemechanic-20200205t162532000z
title
Transaction InfoBlock #40558006/Trx 7965909c39474bce395a0bed9864a88e7a359b17
View Raw JSON Data
{
  "block": 40558006,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @mikethemechanic! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@mikethemechanic/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/@mikethemechanic) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=mikethemechanic)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-a-better-rich-list-comparator\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-a-better-rich-list-comparator\">SteemitBoard Ranking update - A better rich list comparator</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\"]}",
      "parent_author": "mikethemechanic",
      "parent_permlink": "blockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics",
      "permlink": "steemitboard-notify-mikethemechanic-20200205t162532000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-02-05T16:25:33",
  "trx_id": "7965909c39474bce395a0bed9864a88e7a359b17",
  "trx_in_block": 1,
  "virtual_op": 0
}
steemdelegated 5.497 SP to @mikethemechanic
2019/05/30 06:18:30
delegateemikethemechanic
delegatorsteem
vesting shares8941.551074 VESTS
Transaction InfoBlock #33353202/Trx 040b67f9e9fad22550c7c0d21bcc77c1f6b130a0
View Raw JSON Data
{
  "block": 33353202,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "8941.551074 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-30T06:18:30",
  "trx_id": "040b67f9e9fad22550c7c0d21bcc77c1f6b130a0",
  "trx_in_block": 34,
  "virtual_op": 0
}
2019/02/05 17:49:12
authorsteemitboard
bodyCongratulations @mikethemechanic! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@mikethemechanic/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_[Click here to view your Board](https://steemitboard.com/@mikethemechanic)_</sub> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
parent authormikethemechanic
parent permlinkblockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics
permlinksteemitboard-notify-mikethemechanic-20190205t174912000z
title
Transaction InfoBlock #30087550/Trx ad48e3b239d09084849a955f7c0976510994f9cb
View Raw JSON Data
{
  "block": 30087550,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @mikethemechanic! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@mikethemechanic/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_[Click here to view your Board](https://steemitboard.com/@mikethemechanic)_</sub>\n\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "mikethemechanic",
      "parent_permlink": "blockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics",
      "permlink": "steemitboard-notify-mikethemechanic-20190205t174912000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-02-05T17:49:12",
  "trx_id": "ad48e3b239d09084849a955f7c0976510994f9cb",
  "trx_in_block": 12,
  "virtual_op": 0
}
steemdelegated 5.620 SP to @mikethemechanic
2018/06/05 17:33:42
delegateemikethemechanic
delegatorsteem
vesting shares9140.883861 VESTS
Transaction InfoBlock #23062071/Trx 2bc2fe409bc73f5d732da15f86af9056bc69af5d
View Raw JSON Data
{
  "block": 23062071,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "9140.883861 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-06-05T17:33:42",
  "trx_id": "2bc2fe409bc73f5d732da15f86af9056bc69af5d",
  "trx_in_block": 20,
  "virtual_op": 0
}
steemdelegated 18.134 SP to @mikethemechanic
2018/05/19 04:44:51
delegateemikethemechanic
delegatorsteem
vesting shares29496.420588 VESTS
Transaction InfoBlock #22557586/Trx f2589037d3ee32bb028c93839da25a25f6aa3e54
View Raw JSON Data
{
  "block": 22557586,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "mikethemechanic",
      "delegator": "steem",
      "vesting_shares": "29496.420588 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-05-19T04:44:51",
  "trx_id": "f2589037d3ee32bb028c93839da25a25f6aa3e54",
  "trx_in_block": 57,
  "virtual_op": 0
}
2018/03/06 15:00:54
idfollow
json["follow",{"follower":"mikethemechanic","following":"projectpartners","what":["blog"]}]
required auths[]
required posting auths["mikethemechanic"]
Transaction InfoBlock #20440969/Trx 201eee9eb21dab0f9323fae0f4f7e1dcd2e92063
View Raw JSON Data
{
  "block": 20440969,
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"mikethemechanic\",\"following\":\"projectpartners\",\"what\":[\"blog\"]}]",
      "required_auths": [],
      "required_posting_auths": [
        "mikethemechanic"
      ]
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-03-06T15:00:54",
  "trx_id": "201eee9eb21dab0f9323fae0f4f7e1dcd2e92063",
  "trx_in_block": 3,
  "virtual_op": 0
}
2018/03/06 15:00:18
authorprojectpartners
permlinkblockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics
votermikethemechanic
weight10000 (100.00%)
Transaction InfoBlock #20440957/Trx c75bf8d0f77fd84c531a9364056d9d4b613ccb01
View Raw JSON Data
{
  "block": 20440957,
  "op": [
    "vote",
    {
      "author": "projectpartners",
      "permlink": "blockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics",
      "voter": "mikethemechanic",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-03-06T15:00:18",
  "trx_id": "c75bf8d0f77fd84c531a9364056d9d4b613ccb01",
  "trx_in_block": 9,
  "virtual_op": 0
}
2018/03/02 15:01:03
authormikethemechanic
body@@ -10467,18 +10467,16 @@ sform.%0A%0A -** Project @@ -10533,18 +10533,16 @@ enter %0A -** %5Bwww.pro
json metadata{"tags":["blockchain","ethereum","logistic","parcel","smartcontracts"],"image":["https://cdn-images-1.medium.com/max/1400/1*yh2S8IHZP03LUClKrmlLNg.jpeg","https://cdn-images-1.medium.com/max/1400/1*w_8gaA0kzPT2SMWDzsH6YA.jpeg","https://cdn-images-1.medium.com/max/1400/1*Irrj7-IX6iSSnuSmQpeYfw.png","https://cdn-images-1.medium.com/max/1400/1*U90VgO8GRia40zwgtCr8GQ.png","https://cdn-images-1.medium.com/max/1400/1*p1aVBGV9_4JZZr3NqHYpKg.png","https://cdn-images-1.medium.com/max/1400/1*YeiZPjtEX0J5r34bseE9Bg.png"],"links":["https://github.com/ProjectPartnersManagement/","https://github.com/ethereum/web3.js/","https://metamask.io/","https://etherscan.io/","https://www.civic.com/","http://www.project-partners.de/"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkblockchain
permlinkblockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics
titleBlockchain secured parcel service as a complementary business model in logistics
Transaction InfoBlock #20325814/Trx af22e1ae7b2e925b8f5577f1a2ce1b006b690b1e
View Raw JSON Data
{
  "block": 20325814,
  "op": [
    "comment",
    {
      "author": "mikethemechanic",
      "body": "@@ -10467,18 +10467,16 @@\n sform.%0A%0A\n-**\n Project \n@@ -10533,18 +10533,16 @@\n enter  %0A\n-**\n %5Bwww.pro\n",
      "json_metadata": "{\"tags\":[\"blockchain\",\"ethereum\",\"logistic\",\"parcel\",\"smartcontracts\"],\"image\":[\"https://cdn-images-1.medium.com/max/1400/1*yh2S8IHZP03LUClKrmlLNg.jpeg\",\"https://cdn-images-1.medium.com/max/1400/1*w_8gaA0kzPT2SMWDzsH6YA.jpeg\",\"https://cdn-images-1.medium.com/max/1400/1*Irrj7-IX6iSSnuSmQpeYfw.png\",\"https://cdn-images-1.medium.com/max/1400/1*U90VgO8GRia40zwgtCr8GQ.png\",\"https://cdn-images-1.medium.com/max/1400/1*p1aVBGV9_4JZZr3NqHYpKg.png\",\"https://cdn-images-1.medium.com/max/1400/1*YeiZPjtEX0J5r34bseE9Bg.png\"],\"links\":[\"https://github.com/ProjectPartnersManagement/\",\"https://github.com/ethereum/web3.js/\",\"https://metamask.io/\",\"https://etherscan.io/\",\"https://www.civic.com/\",\"http://www.project-partners.de/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "blockchain",
      "permlink": "blockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics",
      "title": "Blockchain secured parcel service as a complementary business model in logistics"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-03-02T15:01:03",
  "trx_id": "af22e1ae7b2e925b8f5577f1a2ce1b006b690b1e",
  "trx_in_block": 10,
  "virtual_op": 0
}
2018/03/01 10:54:18
authormikethemechanic
permlinkblockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics
votersensation
weight10000 (100.00%)
Transaction InfoBlock #20292103/Trx f8eb2759b3b491c5a6e50a3ace47edb4aabae62d
View Raw JSON Data
{
  "block": 20292103,
  "op": [
    "vote",
    {
      "author": "mikethemechanic",
      "permlink": "blockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics",
      "voter": "sensation",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-03-01T10:54:18",
  "trx_id": "f8eb2759b3b491c5a6e50a3ace47edb4aabae62d",
  "trx_in_block": 3,
  "virtual_op": 0
}
2018/03/01 10:09:09
idfollow
json["follow",{"follower":"mikethemechanic","following":"boxmining","what":["blog"]}]
required auths[]
required posting auths["mikethemechanic"]
Transaction InfoBlock #20291200/Trx 0c3492cbdcb8fe30d2a372446dbc3be3dadb5141
View Raw JSON Data
{
  "block": 20291200,
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"mikethemechanic\",\"following\":\"boxmining\",\"what\":[\"blog\"]}]",
      "required_auths": [],
      "required_posting_auths": [
        "mikethemechanic"
      ]
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-03-01T10:09:09",
  "trx_id": "0c3492cbdcb8fe30d2a372446dbc3be3dadb5141",
  "trx_in_block": 1,
  "virtual_op": 0
}
2018/03/01 09:26:24
authormikethemechanic
body## For organizations stepping into the Blockchain it is oftentimes not sufficient to migrate an existing business process. Instead, to leverage the potential of Blockchain technology in breadth and depth, the most relevant opportunities reside beyond current business boundaries within complementary business models. This article describes a Blockchain secured parcel service as an example of how a logistics operator can leverage Blockchain technology to provide a new service to its customers, gain additional market shares and ultimately disrupt the business of internet payment companies. ![](https://cdn-images-1.medium.com/max/1400/1*yh2S8IHZP03LUClKrmlLNg.jpeg) #### Use Case Parcel delivery is a highly optimized and efficient business. It is simple to use for end customers and daily executed by logistics operators all over the world. In essence, the common use case works as follows: 1. Jane wants to send a parcel to John. 2. Logistics operator X picks up the parcel and ensures the transport to John. 3. Upon delivery, John confirms the successfully delivery with a signature typically on an electronic device provided by the operator. 4. The financial transaction is managed by a payment provider. This provider transfers the agreed amount from John to Jane. The business boundaries are well defined. The logistics operator’s business is the transport of parcels whereas the payment provider’s is twofold. First, securing the financial transaction in exchange for a service fee including seller/buyer protection (fraud protection in case Jane send the parcel but John does not transfer the agreed amount of money). And second leveraging certain data points to sell this information to third parties. Neither the logistics operator nor the payment provider has the ability to step into each other’s business. One of the benefits of Blockchain technology is its ability to cut out the middlemen and provide every party in the network access to the same source of truth. Let’s think about this a bit further. The only reason for the logistics operator to cooperate with the payment provider is because the former doesn’t have the capabilities to manage financial transactions. On the other hand, Jane requests buyer protection which is inherently linked to the financial transaction. That is, because the logistics operator controls the transport of the parcel but cannot guarantee that John receives the agreed amount from Jane. The payment provider is the middlemen we want to cut out and enable the logistics operator to execute the entire business process directly with its customers John and Jane. This would be a win-win situation for all remaining parties. The logistics operator could provide a payment service include buyer protection as an additional insurance service without being a payment provider or insurer. John and Jane could execute the sale at lower costs and wouldn’t need to sacrifice their privacy. With said being said, let’s dive into the details of our use case and explore how to use the Blockchain by implementing a decentralized solution on Ethereum. More precisely we’ll build a Smart Contract acting as an escrow service that holds the money of a purchase order until the item is physically shipped to the buyer. To secure this procedure and facilitate usage, the task of initiating the delivery moves from the package sender/seller to the package receiver/buyer: 1. John buys a smartphone from Jane at the price of 200€ via the internet. 2. Jane gives her email and ETH address to John. 3. John opens a shipping order via a smart contract, which is owned by a specific parcel service company, with the following minimal information: a. Email of package sender (seller)_ b. Public ETH address of package sender (seller)_ c. Delivery address of the package (buyer)_ d. Price of the item_ 4. When the price is deposited at the smart contract and the transaction (TXN) is confirmed, the backend of the parcel service creates a shipping order together with a printable label and sends it to the seller’s email address. The shipping order is now directly connected to the specific deposit in the Smart Contract. 5. Jane checks whether the deposit is pointing to her public ETH address by checking the transaction of the ID contained in the email she received. 6. Jane prints the label, sticks it on the package and takes it to the closest parcel counter. 7. Jane’s ID is recorded and connected to the parcel order ID. 8. The parcel service ships the package to John. The delivery agent scans the label on the package and hands it over to John. This action triggers the smart contract and the deposit connected to this shipment is transferred to Jane’s ETH address. ### Technical Components Our implementation is comprised of the following technical components. You can find the source code for all four components on our [GitHub](https://github.com/ProjectPartnersManagement/). Please note that this code is just a proof of concept, has not been tested comprehensively and may have several vulnerabilities. Don’t use it in real life. #### Smart Contract The Smart Contract (the escrow service) implements five basic functions: ![](https://cdn-images-1.medium.com/max/1400/1*w_8gaA0kzPT2SMWDzsH6YA.jpeg) #### User Interface / Website The user interface is a website hosted by the parcel service. It is built with HTML, CSS, and JavaScript with a [web3.js](https://github.com/ethereum/web3.js/) integration that points to the Ethereum full node of the parcel service. As a proof of concept, we implemented an integration with the [METAMASK wallet](https://metamask.io/). #### Backend Service The backend service listens to smart contract events. It generates the shipping orders and sends an email to the package sender. The backend triggers 2 out of 4 states of the smart contract. These states are *Package posted at package station* and *Package delivered to the recipient* #### Blockchain Explorer The Blockchain explorer allows transactions to be verified. Any Blockchain explorer such as [etherscan.io](https://etherscan.io/) can be used. #### Usage Usage of the new service is straightforward to both end customers and the logistics operator. 1. John registers a new shipment on the operator’s website and submits the agreed amount to the smart contract ![](https://cdn-images-1.medium.com/max/1400/1*Irrj7-IX6iSSnuSmQpeYfw.png) 2\. Jane received an email containing a bar code to be printed out and stick onto the parcel ![](https://cdn-images-1.medium.com/max/1400/1*U90VgO8GRia40zwgtCr8GQ.png) 3\. The logistics operator acknowledges receipt of the parcel ![](https://cdn-images-1.medium.com/max/1400/1*p1aVBGV9_4JZZr3NqHYpKg.png) 4\. The logistics operator confirms the delivery of the parcel ![](https://cdn-images-1.medium.com/max/1400/1*YeiZPjtEX0J5r34bseE9Bg.png) 5\. John receives the payment on his ETH address ### Questions Discussing this use case with logistics operators we ran into various conceptual questions we’d like to share as well. **How is the package delivery tracked reliably?** You need a reliable off-chain trigger, that tells the Smart Contract to transfer the deposit when the package is delivered. This so-called “oracle” is the delivery agent who hands over the package to the buyer or to a self-service package station. This event can be secured using a multi-signature procedure if necessary. In this process, the delivery agent is a reliable oracle as his only intention is package delivery. He will not benefit from any form of manipulation. **What if the seller doesn’t send the package, are the funds locked forever?** The Smart Contract comes with a timer function. Once the contract is funded, the seller has a timeframe of x weeks (we chose a timer of two weeks) to hand over the package to the parcel service. When the deadline expires, the shipping order is invalidated, the funds are returned to their sender and the parcel service will not accept the package label with this specific ID. **How can we guarantee that the package contains the agreed goods, in this case a smart phone?** This cannot be guaranteed with this escrow procedure nor with any other service. As an additional layer of fraud protection, the parcel service could ask for the ID of the package sender and record this information for the time of the delivery. **Can someone see the customer’s data on the Blockchain?** The procedure will not store any personal data such as address information on the Blockchain but a cryptographically secure hash value. Only the logistics operator can link this hash to a postal address. In case of even more stringent privacy constraints, the identity of the seller could be entirely hidden to the operator. It would only be revealed by either the seller or buyer in case of fraud leveraging an Identification service such as [CIVIC](https://www.civic.com/). **How can I make sure that the smart contract works as expected?** The logistic operator publishes the smart contract’s source code. With this information at hand, you can easily compile the source code to verify that the resulting byte code equals the smart contract’s byte code saved on the Blockchain. ### Conclusion We demonstrated how just a few lines of code can easily disrupt well established business models. By eliminating the middleman in the form of the payment provider, the logistics operator can offer additional value add services to its customers at lower costs and higher privacy. The operator shifted existing business boundaries and created a complementary business model using Blockchain technology. Since the operator has absolutely no access to the funding inside the smart contract, there is no need to fulfill any extra financial or insurance regulations. The contract is peer-to-peer between buyer and seller. Both accept the logistics operator to act as a non-partisan trigger. The concept is also applicable to post-paid orders. The inherent issue with trust and fraud is solved by tying the transfer of money and the shipment to intrinsic motivations. ### About us The Project Partners Blockchain Competence Center is dedicated to help organizations finding their way into the Blockchain. We believe that Blockchain technology will change the way we live and work. It is our mission to participate in this change and enable organizations to transform. **Project Partners Management GmbH | Blockchain Competence Center **[www.project-partners.de](http://www.project-partners.de/)
json metadata{"tags":["blockchain","ethereum","logistic","parcel","smartcontracts"],"image":["https://cdn-images-1.medium.com/max/1400/1*yh2S8IHZP03LUClKrmlLNg.jpeg","https://cdn-images-1.medium.com/max/1400/1*w_8gaA0kzPT2SMWDzsH6YA.jpeg","https://cdn-images-1.medium.com/max/1400/1*Irrj7-IX6iSSnuSmQpeYfw.png","https://cdn-images-1.medium.com/max/1400/1*U90VgO8GRia40zwgtCr8GQ.png","https://cdn-images-1.medium.com/max/1400/1*p1aVBGV9_4JZZr3NqHYpKg.png","https://cdn-images-1.medium.com/max/1400/1*YeiZPjtEX0J5r34bseE9Bg.png"],"links":["https://github.com/ProjectPartnersManagement/","https://github.com/ethereum/web3.js/","https://metamask.io/","https://etherscan.io/","https://www.civic.com/","http://www.project-partners.de/"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkblockchain
permlinkblockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics
titleBlockchain secured parcel service as a complementary business model in logistics
Transaction InfoBlock #20290347/Trx d92b2569ac6b8134efdb4a6579a1bf0ebb828839
View Raw JSON Data
{
  "block": 20290347,
  "op": [
    "comment",
    {
      "author": "mikethemechanic",
      "body": "## For organizations stepping into the Blockchain it is oftentimes not sufficient to migrate an existing business process. Instead, to leverage the potential of Blockchain technology in breadth and depth, the most relevant opportunities reside beyond current business boundaries within complementary business models. This article describes a Blockchain secured parcel service as an example of how a logistics operator can leverage Blockchain technology to provide a new service to its customers, gain additional market shares and ultimately disrupt the business of internet payment companies.\n\n![](https://cdn-images-1.medium.com/max/1400/1*yh2S8IHZP03LUClKrmlLNg.jpeg)\n\n#### Use Case\n\nParcel delivery is a highly optimized and efficient business. It is simple to use for end customers and daily executed by logistics operators all over the world. In essence, the common use case works as follows:\n\n1.  Jane wants to send a parcel to John.\n2.  Logistics operator X picks up the parcel and ensures the transport to John.\n3.  Upon delivery, John confirms the successfully delivery with a signature typically on an electronic device provided by the operator.\n4.  The financial transaction is managed by a payment provider. This provider transfers the agreed amount from John to Jane.\n\nThe business boundaries are well defined. The logistics operator’s business is the transport of parcels whereas the payment provider’s is twofold. First, securing the financial transaction in exchange for a service fee including seller/buyer protection (fraud protection in case Jane send the parcel but John does not transfer the agreed amount of money). And second leveraging certain data points to sell this information to third parties. Neither the logistics operator nor the payment provider has the ability to step into each other’s business.\n\nOne of the benefits of Blockchain technology is its ability to cut out the middlemen and provide every party in the network access to the same source of truth. Let’s think about this a bit further. The only reason for the logistics operator to cooperate with the payment provider is because the former doesn’t have the capabilities to manage financial transactions. On the other hand, Jane requests buyer protection which is inherently linked to the financial transaction. That is, because the logistics operator controls the transport of the parcel but cannot guarantee that John receives the agreed amount from Jane. The payment provider is the middlemen we want to cut out and enable the logistics operator to execute the entire business process directly with its customers John and Jane. This would be a win-win situation for all remaining parties. The logistics operator could provide a payment service include buyer protection as an additional insurance service without being a payment provider or insurer. John and Jane could execute the sale at lower costs and wouldn’t need to sacrifice their privacy.\n\nWith said being said, let’s dive into the details of our use case and explore how to use the Blockchain by implementing a decentralized solution on Ethereum. More precisely we’ll build a Smart Contract acting as an escrow service that holds the money of a purchase order until the item is physically shipped to the buyer. To secure this procedure and facilitate usage, the task of initiating the delivery moves from the package sender/seller to the package receiver/buyer:\n\n 1. John buys a smartphone from Jane at the price of 200€ via the\n    internet.\n 2. Jane gives her email and ETH address to John.\n 3. John opens a shipping order via a smart contract, which is owned\n        by a specific parcel service company, with the following minimal\n        information:\n\n\ta. Email of package sender (seller)_\n\n\tb. Public ETH address of package sender (seller)_\n\n\tc. Delivery address of the package (buyer)_\n\n\td. Price of the item_\n\n 4. When the price is deposited at the smart contract and the\n    transaction (TXN) is confirmed, the backend of the parcel service\n    creates a shipping order together with a printable label and sends\n    it to the seller’s email address. The shipping order is now directly\n    connected to the specific deposit in the Smart Contract.\n\n 5. Jane checks whether the deposit is pointing to her public ETH\n    address by checking the transaction of the ID contained in the email\n    she received.\n\n 6. Jane prints the label, sticks it on the package and takes it to the\n    closest parcel counter.\n\n 7. Jane’s ID is recorded and connected to the parcel order ID.\n\n 8. The parcel service ships the package to John. The delivery agent\n    scans the label on the package and hands it over to John. This\n    action triggers the smart contract and the deposit connected to this\n    shipment is transferred to Jane’s ETH address.\n\n### Technical Components\n\nOur implementation is comprised of the following technical components. You can find the source code for all four components on our  [GitHub](https://github.com/ProjectPartnersManagement/). Please note that this code is just a proof of concept, has not been tested comprehensively and may have several vulnerabilities. Don’t use it in real life.\n\n#### Smart Contract\n\nThe Smart Contract (the escrow service) implements five basic functions:\n\n![](https://cdn-images-1.medium.com/max/1400/1*w_8gaA0kzPT2SMWDzsH6YA.jpeg)\n\n#### User Interface / Website\n\nThe user interface is a website hosted by the parcel service. It is built with HTML, CSS, and JavaScript with a  [web3.js](https://github.com/ethereum/web3.js/)  integration that points to the Ethereum full node of the parcel service. As a proof of concept, we implemented an integration with the  [METAMASK wallet](https://metamask.io/).\n\n#### Backend Service\n\nThe backend service listens to smart contract events. It generates the shipping orders and sends an email to the package sender.\n\nThe backend triggers 2 out of 4 states of the smart contract. These states are *Package posted at package station* and *Package delivered to the recipient*\n\n#### Blockchain Explorer\n\nThe Blockchain explorer allows transactions to be verified. Any Blockchain explorer such as  [etherscan.io](https://etherscan.io/)  can be used.\n\n#### Usage\n\nUsage of the new service is straightforward to both end customers and the logistics operator.\n\n1.  John registers a new shipment on the operator’s website and submits the agreed amount to the smart contract\n\n![](https://cdn-images-1.medium.com/max/1400/1*Irrj7-IX6iSSnuSmQpeYfw.png)\n\n2\\. Jane received an email containing a bar code to be printed out and stick onto the parcel\n\n![](https://cdn-images-1.medium.com/max/1400/1*U90VgO8GRia40zwgtCr8GQ.png)\n\n3\\. The logistics operator acknowledges receipt of the parcel\n\n![](https://cdn-images-1.medium.com/max/1400/1*p1aVBGV9_4JZZr3NqHYpKg.png)\n\n4\\. The logistics operator confirms the delivery of the parcel\n\n![](https://cdn-images-1.medium.com/max/1400/1*YeiZPjtEX0J5r34bseE9Bg.png)\n\n5\\. John receives the payment on his ETH address\n\n### Questions\n\nDiscussing this use case with logistics operators we ran into various conceptual questions we’d like to share as well.\n\n**How is the package delivery tracked reliably?**\n\nYou need a reliable off-chain trigger, that tells the Smart Contract to transfer the deposit when the package is delivered. This so-called “oracle” is the delivery agent who hands over the package to the buyer or to a self-service package station. This event can be secured using a multi-signature procedure if necessary. In this process, the delivery agent is a reliable oracle as his only intention is package delivery. He will not benefit from any form of manipulation.\n\n**What if the seller doesn’t send the package, are the funds locked forever?**\n\nThe Smart Contract comes with a timer function. Once the contract is funded, the seller has a timeframe of x weeks (we chose a timer of two weeks) to hand over the package to the parcel service. When the deadline expires, the shipping order is invalidated, the funds are returned to their sender and the parcel service will not accept the package label with this specific ID.\n\n**How can we guarantee that the package contains the agreed goods, in this case a smart phone?**\n\nThis cannot be guaranteed with this escrow procedure nor with any other service. As an additional layer of fraud protection, the parcel service could ask for the ID of the package sender and record this information for the time of the delivery.\n\n**Can someone see the customer’s data on the Blockchain?**\n\nThe procedure will not store any personal data such as address information on the Blockchain but a cryptographically secure hash value. Only the logistics operator can link this hash to a postal address. In case of even more stringent privacy constraints, the identity of the seller could be entirely hidden to the operator. It would only be revealed by either the seller or buyer in case of fraud leveraging an Identification service such as  [CIVIC](https://www.civic.com/).\n\n**How can I make sure that the smart contract works as expected?**\n\nThe logistic operator publishes the smart contract’s source code. With this information at hand, you can easily compile the source code to verify that the resulting byte code equals the smart contract’s byte code saved on the Blockchain.\n\n### Conclusion\n\nWe demonstrated how just a few lines of code can easily disrupt well established business models. By eliminating the middleman in the form of the payment provider, the logistics operator can offer additional value add services to its customers at lower costs and higher privacy. The operator shifted existing business boundaries and created a complementary business model using Blockchain technology.\n\nSince the operator has absolutely no access to the funding inside the smart contract, there is no need to fulfill any extra financial or insurance regulations. The contract is peer-to-peer between buyer and seller. Both accept the logistics operator to act as a non-partisan trigger. The concept is also applicable to post-paid orders. The inherent issue with trust and fraud is solved by tying the transfer of money and the shipment to intrinsic motivations.\n\n### About us\n\nThe Project Partners Blockchain Competence Center is dedicated to help organizations finding their way into the Blockchain. We believe that Blockchain technology will change the way we live and work. It is our mission to participate in this change and enable organizations to transform.\n\n**Project Partners Management GmbH | Blockchain Competence Center  \n**[www.project-partners.de](http://www.project-partners.de/)",
      "json_metadata": "{\"tags\":[\"blockchain\",\"ethereum\",\"logistic\",\"parcel\",\"smartcontracts\"],\"image\":[\"https://cdn-images-1.medium.com/max/1400/1*yh2S8IHZP03LUClKrmlLNg.jpeg\",\"https://cdn-images-1.medium.com/max/1400/1*w_8gaA0kzPT2SMWDzsH6YA.jpeg\",\"https://cdn-images-1.medium.com/max/1400/1*Irrj7-IX6iSSnuSmQpeYfw.png\",\"https://cdn-images-1.medium.com/max/1400/1*U90VgO8GRia40zwgtCr8GQ.png\",\"https://cdn-images-1.medium.com/max/1400/1*p1aVBGV9_4JZZr3NqHYpKg.png\",\"https://cdn-images-1.medium.com/max/1400/1*YeiZPjtEX0J5r34bseE9Bg.png\"],\"links\":[\"https://github.com/ProjectPartnersManagement/\",\"https://github.com/ethereum/web3.js/\",\"https://metamask.io/\",\"https://etherscan.io/\",\"https://www.civic.com/\",\"http://www.project-partners.de/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "blockchain",
      "permlink": "blockchain-secured-parcel-service-as-a-complementary-business-model-in-logistics",
      "title": "Blockchain secured parcel service as a complementary business model in logistics"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-03-01T09:26:24",
  "trx_id": "d92b2569ac6b8134efdb4a6579a1bf0ebb828839",
  "trx_in_block": 33,
  "virtual_op": 0
}
mikethemechanicupdated their account properties
2018/02/06 10:47:36
accountmikethemechanic
json metadata{"profile":{"name":"MikeTheMechanic","location":"Germany","profile_image":"https://s10.postimg.org/7dc9wx2uh/klein.jpg"}}
memo keySTM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv
Transaction InfoBlock #19630293/Trx cb8bfae26fc9c2d43b8a39fc8a009fb375a09876
View Raw JSON Data
{
  "block": 19630293,
  "op": [
    "account_update",
    {
      "account": "mikethemechanic",
      "json_metadata": "{\"profile\":{\"name\":\"MikeTheMechanic\",\"location\":\"Germany\",\"profile_image\":\"https://s10.postimg.org/7dc9wx2uh/klein.jpg\"}}",
      "memo_key": "STM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-02-06T10:47:36",
  "trx_id": "cb8bfae26fc9c2d43b8a39fc8a009fb375a09876",
  "trx_in_block": 44,
  "virtual_op": 0
}
mikethemechanicupdated their account properties
2018/02/06 10:46:03
accountmikethemechanic
json metadata{"profile":{"name":"MikeTheMechanic","location":"Germany","profile_image":"https://postimg.org/image/smzw7rj51/"}}
memo keySTM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv
Transaction InfoBlock #19630262/Trx ea3a716dc67a87003735f30cd2646e8a3d73caa1
View Raw JSON Data
{
  "block": 19630262,
  "op": [
    "account_update",
    {
      "account": "mikethemechanic",
      "json_metadata": "{\"profile\":{\"name\":\"MikeTheMechanic\",\"location\":\"Germany\",\"profile_image\":\"https://postimg.org/image/smzw7rj51/\"}}",
      "memo_key": "STM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-02-06T10:46:03",
  "trx_id": "ea3a716dc67a87003735f30cd2646e8a3d73caa1",
  "trx_in_block": 35,
  "virtual_op": 0
}
mikethemechanicupdated their account properties
2018/02/06 10:41:42
accountmikethemechanic
json metadata{"profile":{"name":"MikeTheMechanic","location":"Germany"}}
memo keySTM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv
Transaction InfoBlock #19630175/Trx ff6dd1cd63c58e3fd942f5eb6eb438c8f842b775
View Raw JSON Data
{
  "block": 19630175,
  "op": [
    "account_update",
    {
      "account": "mikethemechanic",
      "json_metadata": "{\"profile\":{\"name\":\"MikeTheMechanic\",\"location\":\"Germany\"}}",
      "memo_key": "STM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-02-06T10:41:42",
  "trx_id": "ff6dd1cd63c58e3fd942f5eb6eb438c8f842b775",
  "trx_in_block": 12,
  "virtual_op": 0
}
mikethemechanicupdated their account properties
2018/02/06 10:41:03
accountmikethemechanic
json metadata{"profile":{"location":"Germany"}}
memo keySTM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv
Transaction InfoBlock #19630162/Trx 7bdfd19eafc38b949f091265e649657b607776d2
View Raw JSON Data
{
  "block": 19630162,
  "op": [
    "account_update",
    {
      "account": "mikethemechanic",
      "json_metadata": "{\"profile\":{\"location\":\"Germany\"}}",
      "memo_key": "STM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-02-06T10:41:03",
  "trx_id": "7bdfd19eafc38b949f091265e649657b607776d2",
  "trx_in_block": 50,
  "virtual_op": 0
}
steemcreated a new account: @mikethemechanic
2018/02/05 14:06:09
active{"account_auths":[],"key_auths":[["STM8DLbm7LdQo4SBQYQWvqRTtBTfkTW8qrQTQXBjRV2Vcf6CojYz7",1]],"weight_threshold":1}
creatorsteem
delegation29700.000000 VESTS
extensions[]
fee0.500 STEEM
json metadata
memo keySTM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv
new account namemikethemechanic
owner{"account_auths":[],"key_auths":[["STM78BKfUMdUMEWNUnQEqfW4oowYPB97HoNkFpTXeeYbgW6w5EdBN",1]],"weight_threshold":1}
posting{"account_auths":[],"key_auths":[["STM6ysoVQwqSsarinZQv3x3rjKMDCNP7o5xXo7ZQoEPjA1N4oo6VT",1]],"weight_threshold":1}
Transaction InfoBlock #19605470/Trx 8eed33e72dd8010c0bf907b97d3c47f3317a9252
View Raw JSON Data
{
  "block": 19605470,
  "op": [
    "account_create_with_delegation",
    {
      "active": {
        "account_auths": [],
        "key_auths": [
          [
            "STM8DLbm7LdQo4SBQYQWvqRTtBTfkTW8qrQTQXBjRV2Vcf6CojYz7",
            1
          ]
        ],
        "weight_threshold": 1
      },
      "creator": "steem",
      "delegation": "29700.000000 VESTS",
      "extensions": [],
      "fee": "0.500 STEEM",
      "json_metadata": "",
      "memo_key": "STM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv",
      "new_account_name": "mikethemechanic",
      "owner": {
        "account_auths": [],
        "key_auths": [
          [
            "STM78BKfUMdUMEWNUnQEqfW4oowYPB97HoNkFpTXeeYbgW6w5EdBN",
            1
          ]
        ],
        "weight_threshold": 1
      },
      "posting": {
        "account_auths": [],
        "key_auths": [
          [
            "STM6ysoVQwqSsarinZQv3x3rjKMDCNP7o5xXo7ZQoEPjA1N4oo6VT",
            1
          ]
        ],
        "weight_threshold": 1
      }
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-02-05T14:06:09",
  "trx_id": "8eed33e72dd8010c0bf907b97d3c47f3317a9252",
  "trx_in_block": 9,
  "virtual_op": 0
}

Account Metadata

POSTING JSON METADATA
profile{"name":"MikeTheMechanic","location":"Germany","profile_image":"https://i.postimg.cc/K8hgSdLJ/Bild1.png","cover_image":"https://i.postimg.cc/K8hgSdLJ/Bild1.png","version":2}
JSON METADATA
profile{"name":"MikeTheMechanic","location":"Germany","profile_image":"https://s10.postimg.org/7dc9wx2uh/klein.jpg"}
{
  "posting_json_metadata": {
    "profile": {
      "name": "MikeTheMechanic",
      "location": "Germany",
      "profile_image": "https://i.postimg.cc/K8hgSdLJ/Bild1.png",
      "cover_image": "https://i.postimg.cc/K8hgSdLJ/Bild1.png",
      "version": 2
    }
  },
  "json_metadata": {
    "profile": {
      "name": "MikeTheMechanic",
      "location": "Germany",
      "profile_image": "https://s10.postimg.org/7dc9wx2uh/klein.jpg"
    }
  }
}

Auth Keys

Owner
Single Signature
Public Keys
STM78BKfUMdUMEWNUnQEqfW4oowYPB97HoNkFpTXeeYbgW6w5EdBN1/1
Active
Single Signature
Public Keys
STM8DLbm7LdQo4SBQYQWvqRTtBTfkTW8qrQTQXBjRV2Vcf6CojYz71/1
Posting
Single Signature
Public Keys
STM6ysoVQwqSsarinZQv3x3rjKMDCNP7o5xXo7ZQoEPjA1N4oo6VT1/1
Memo
STM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv
{
  "owner": {
    "account_auths": [],
    "key_auths": [
      [
        "STM78BKfUMdUMEWNUnQEqfW4oowYPB97HoNkFpTXeeYbgW6w5EdBN",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "active": {
    "account_auths": [],
    "key_auths": [
      [
        "STM8DLbm7LdQo4SBQYQWvqRTtBTfkTW8qrQTQXBjRV2Vcf6CojYz7",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "posting": {
    "account_auths": [],
    "key_auths": [
      [
        "STM6ysoVQwqSsarinZQv3x3rjKMDCNP7o5xXo7ZQoEPjA1N4oo6VT",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "memo": "STM5HWgJLzRhvqZFLoFPgK7pyaDekf4dNabasANhmXHJ8ZNM9dsZv"
}

Witness Votes

0 / 30
No active witness votes.
[]