Ecoer Logo
VOTING POWER0.00%
DOWNVOTE POWER0.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS83.12%
Net Worth
11.804USD
STEEM
218.209STEEM
SBD
0.002SBD
Own SP
0.000SP

Detailed Balance

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

Account Info

namecmhate
id1458283
rank1,813,194
reputation15976089667368
created2020-12-19T06:51:54
recovery_accountsteem
proxyNone
post_count28
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2021-04-04T15:03:06
last_root_post2021-04-04T15:03:06
last_vote_time1970-01-01T00:00:00
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power0
delayed_votes0
balance218.209 STEEM
savings_balance0.000 STEEM
sbd_balance0.002 SBD
savings_sbd_balance0.000 SBD
vesting_shares0.000000 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares0.000000 VESTS
reward_vesting_balance0.000000 VESTS
vesting_balance0.000 STEEM
vesting_withdraw_rate0.000000 VESTS
next_vesting_withdrawal1969-12-31T23:59:59
withdrawn406245066673
to_withdraw406245066673
withdraw_routes0
savings_withdraw_requests0
last_account_recovery1970-01-01T00:00:00
reset_accountnull
last_owner_update1970-01-01T00:00:00
last_account_update1970-01-01T00:00:00
minedNo
sbd_seconds1,435,023
sbd_last_interest_payment2021-07-11T02:48:54
savings_sbd_last_interest_payment1970-01-01T00:00:00
{
  "id": 1458283,
  "name": "cmhate",
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM5sy5sD49nEwAAucKGZqGQzUpFa5DH7AYMSvS3j4t81EPHcKbHM",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM55mYp7tMkJpKdrVFhFB11actS5nUk8PUwka8vF9ZsAoER36Cir",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7s1dgt4yLwe6QLAzpQwYjjXoZkEvYfVcGJjkDARaPRSFv7BeFh",
        1
      ]
    ]
  },
  "memo_key": "STM7M32PsYg9AeBnrcYMwddhZUtaC7D2QVf85bqUy6Uc2mEm7hZfQ",
  "json_metadata": "{}",
  "posting_json_metadata": "",
  "proxy": "",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_account_update": "1970-01-01T00:00:00",
  "created": "2020-12-19T06:51:54",
  "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": 28,
  "can_vote": true,
  "voting_manabar": {
    "current_mana": "406245066673",
    "last_update_time": 1618164501
  },
  "downvote_manabar": {
    "current_mana": "101561266667",
    "last_update_time": 1618164501
  },
  "voting_power": 0,
  "balance": "218.209 STEEM",
  "savings_balance": "0.000 STEEM",
  "sbd_balance": "0.002 SBD",
  "sbd_seconds": "1435023",
  "sbd_seconds_last_update": "2021-07-11T02:50:18",
  "sbd_last_interest_payment": "2021-07-11T02:48:54",
  "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": "0.000000 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "0.000000 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "withdrawn": "406245066673",
  "to_withdraw": "406245066673",
  "withdraw_routes": 0,
  "curation_rewards": 0,
  "posting_rewards": 1045650,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "witnesses_voted_for": 0,
  "last_post": "2021-04-04T15:03:06",
  "last_root_post": "2021-04-04T15:03:06",
  "last_vote_time": "1970-01-01T00:00:00",
  "post_bandwidth": 0,
  "pending_claimed_accounts": 0,
  "vesting_balance": "0.000 STEEM",
  "reputation": "15976089667368",
  "transfer_history": [],
  "market_history": [],
  "post_history": [],
  "vote_history": [],
  "other_history": [],
  "witness_votes": [],
  "tags_usage": [],
  "guest_bloggers": [],
  "rank": 1813194
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
cmhatereceived 54.493 STEEM from power down installment (62.369 SP)
2021/08/08 02:50:54
from accountcmhate
to accountcmhate
withdrawn101561.266666 VESTS
deposited54.493 STEEM
Transaction InfoBlock #56174740/Virtual Operation #2
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 56174740,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2021-08-08T02:50:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "cmhate",
      "to_account": "cmhate",
      "withdrawn": "101561.266666 VESTS",
      "deposited": "54.493 STEEM"
    }
  ]
}
cmhatereceived 54.457 STEEM from power down installment (62.369 SP)
2021/08/01 02:50:54
from accountcmhate
to accountcmhate
withdrawn101561.266669 VESTS
deposited54.457 STEEM
Transaction InfoBlock #55974597/Virtual Operation #2
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 55974597,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2021-08-01T02:50:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "cmhate",
      "to_account": "cmhate",
      "withdrawn": "101561.266669 VESTS",
      "deposited": "54.457 STEEM"
    }
  ]
}
cmhatereceived 54.420 STEEM from power down installment (62.369 SP)
2021/07/25 02:50:54
from accountcmhate
to accountcmhate
withdrawn101561.266669 VESTS
deposited54.420 STEEM
Transaction InfoBlock #55774336/Virtual Operation #2
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 55774336,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2021-07-25T02:50:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "cmhate",
      "to_account": "cmhate",
      "withdrawn": "101561.266669 VESTS",
      "deposited": "54.420 STEEM"
    }
  ]
}
cmhatereceived 54.383 STEEM from power down installment (62.369 SP)
2021/07/18 02:50:54
from accountcmhate
to accountcmhate
withdrawn101561.266669 VESTS
deposited54.383 STEEM
Transaction InfoBlock #55576788/Virtual Operation #55
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 55576788,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 55,
  "timestamp": "2021-07-18T02:50:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "cmhate",
      "to_account": "cmhate",
      "withdrawn": "101561.266669 VESTS",
      "deposited": "54.383 STEEM"
    }
  ]
}
cmhatesent 710.000 STEEM to @huobi-pro- "323402"
2021/07/11 02:51:15
fromcmhate
tohuobi-pro
amount710.000 STEEM
memo323402
Transaction InfoBlock #55376594/Trx c52600b070f52fbbb930ec1cc06960bc0be83b16
View Raw JSON Data
{
  "trx_id": "c52600b070f52fbbb930ec1cc06960bc0be83b16",
  "block": 55376594,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-07-11T02:51:15",
  "op": [
    "transfer",
    {
      "from": "cmhate",
      "to": "huobi-pro",
      "amount": "710.000 STEEM",
      "memo": "323402"
    }
  ]
}
cmhatestarted power down of 249.474 SP
2021/07/11 02:50:54
accountcmhate
vesting shares406245.066673 VESTS
Transaction InfoBlock #55376587/Trx b3de9b6252510754aa6551b677ee06e882c0302b
View Raw JSON Data
{
  "trx_id": "b3de9b6252510754aa6551b677ee06e882c0302b",
  "block": 55376587,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-07-11T02:50:54",
  "op": [
    "withdraw_vesting",
    {
      "account": "cmhate",
      "vesting_shares": "406245.066673 VESTS"
    }
  ]
}
cmhatebought 3.154 SBD for 42.109 STEEM from @cmhate
2021/07/11 02:50:21
current ownernebula-ai
current orderid2664586700
current pays42.109 STEEM
open ownercmhate
open orderid1625971815
open pays3.154 SBD
Transaction InfoBlock #55376576/Trx 4e1f4d415ec46e0b758c19707d857eee64c6e174
View Raw JSON Data
{
  "trx_id": "4e1f4d415ec46e0b758c19707d857eee64c6e174",
  "block": 55376576,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 1,
  "timestamp": "2021-07-11T02:50:21",
  "op": [
    "fill_order",
    {
      "current_owner": "nebula-ai",
      "current_orderid": 2664586700,
      "current_pays": "42.109 STEEM",
      "open_owner": "cmhate",
      "open_orderid": 1625971815,
      "open_pays": "3.154 SBD"
    }
  ]
}
cmhateblockchain operation: limit order create
2021/07/11 02:50:18
ownercmhate
orderid1625971815
amount to sell53.147 SBD
min to receive709.573 STEEM
fill or killfalse
expiration2021-08-07T02:49:57
Transaction InfoBlock #55376575/Trx af8a19a6772fcd6ec05fecabe0ab0bbe9954ac2d
View Raw JSON Data
{
  "trx_id": "af8a19a6772fcd6ec05fecabe0ab0bbe9954ac2d",
  "block": 55376575,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-07-11T02:50:18",
  "op": [
    "limit_order_create",
    {
      "owner": "cmhate",
      "orderid": 1625971815,
      "amount_to_sell": "53.147 SBD",
      "min_to_receive": "709.573 STEEM",
      "fill_or_kill": false,
      "expiration": "2021-08-07T02:49:57"
    }
  ]
}
cmhatebought 667.464 STEEM for 49.993 SBD from @fenrir78
2021/07/11 02:50:18
current ownercmhate
current orderid1625971815
current pays49.993 SBD
open ownerfenrir78
open orderid1625970898
open pays667.464 STEEM
Transaction InfoBlock #55376575/Trx af8a19a6772fcd6ec05fecabe0ab0bbe9954ac2d
View Raw JSON Data
{
  "trx_id": "af8a19a6772fcd6ec05fecabe0ab0bbe9954ac2d",
  "block": 55376575,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 1,
  "timestamp": "2021-07-11T02:50:18",
  "op": [
    "fill_order",
    {
      "current_owner": "cmhate",
      "current_orderid": 1625971815,
      "current_pays": "49.993 SBD",
      "open_owner": "fenrir78",
      "open_orderid": 1625970898,
      "open_pays": "667.464 STEEM"
    }
  ]
}
cmhateblockchain operation: limit order cancel
2021/07/11 02:49:51
ownercmhate
orderid1625971691
Transaction InfoBlock #55376566/Trx 73056f518011b458f5507aad2792ee2c90d253dc
View Raw JSON Data
{
  "trx_id": "73056f518011b458f5507aad2792ee2c90d253dc",
  "block": 55376566,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-07-11T02:49:51",
  "op": [
    "limit_order_cancel",
    {
      "owner": "cmhate",
      "orderid": 1625971691
    }
  ]
}
cmhateblockchain operation: limit order create
2021/07/11 02:48:54
ownercmhate
orderid1625971691
amount to sell53.149 SBD
min to receive736.289 STEEM
fill or killfalse
expiration2021-08-07T02:47:51
Transaction InfoBlock #55376547/Trx adf3be11b837f0d1fbeab626ab005a60d8292c37
View Raw JSON Data
{
  "trx_id": "adf3be11b837f0d1fbeab626ab005a60d8292c37",
  "block": 55376547,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-07-11T02:48:54",
  "op": [
    "limit_order_create",
    {
      "owner": "cmhate",
      "orderid": 1625971691,
      "amount_to_sell": "53.149 SBD",
      "min_to_receive": "736.289 STEEM",
      "fill_or_kill": false,
      "expiration": "2021-08-07T02:47:51"
    }
  ]
}
cmhateclaimed reward balance: 31.000 SBD, 29.586 SP
2021/04/11 18:08:21
accountcmhate
reward steem0.000 STEEM
reward sbd31.000 SBD
reward vests48177.206327 VESTS
Transaction InfoBlock #52800876/Trx 525c2b8eca3db64384122b97e3a0cb10298b9833
View Raw JSON Data
{
  "trx_id": "525c2b8eca3db64384122b97e3a0cb10298b9833",
  "block": 52800876,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-11T18:08:21",
  "op": [
    "claim_reward_balance",
    {
      "account": "cmhate",
      "reward_steem": "0.000 STEEM",
      "reward_sbd": "31.000 SBD",
      "reward_vests": "48177.206327 VESTS"
    }
  ]
}
2021/04/11 15:03:06
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
sbd payout31.000 SBD
steem payout0.000 STEEM
vesting payout48177.206327 VESTS
Transaction InfoBlock #52797204/Virtual Operation #11
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 52797204,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 11,
  "timestamp": "2021-04-11T15:03:06",
  "op": [
    "author_reward",
    {
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "sbd_payout": "31.000 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "48177.206327 VESTS"
    }
  ]
}
cmhateclaimed reward balance: 22.143 SBD, 26.398 SP
2021/04/10 16:53:54
accountcmhate
reward steem0.000 STEEM
reward sbd22.143 SBD
reward vests42987.064758 VESTS
Transaction InfoBlock #52770878/Trx 755d54053fc06af2de1fed7966bce3fe7c81c9dc
View Raw JSON Data
{
  "trx_id": "755d54053fc06af2de1fed7966bce3fe7c81c9dc",
  "block": 52770878,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-10T16:53:54",
  "op": [
    "claim_reward_balance",
    {
      "account": "cmhate",
      "reward_steem": "0.000 STEEM",
      "reward_sbd": "22.143 SBD",
      "reward_vests": "42987.064758 VESTS"
    }
  ]
}
cmhatereceived 22.143 SBD, 26.398 SP author reward for @cmhate / the-value-path-of-big-data
2021/04/09 13:39:21
authorcmhate
permlinkthe-value-path-of-big-data
sbd payout22.143 SBD
steem payout0.000 STEEM
vesting payout42987.064758 VESTS
Transaction InfoBlock #52738483/Virtual Operation #13
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 52738483,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 13,
  "timestamp": "2021-04-09T13:39:21",
  "op": [
    "author_reward",
    {
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "sbd_payout": "22.143 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "42987.064758 VESTS"
    }
  ]
}
cmhatesent 1,183.000 STEEM to @huobi-pro- "323402"
2021/04/09 09:45:00
fromcmhate
tohuobi-pro
amount1183.000 STEEM
memo323402
Transaction InfoBlock #52733843/Trx 12648abe21c92c510b5bd3aab16899568938444f
View Raw JSON Data
{
  "trx_id": "12648abe21c92c510b5bd3aab16899568938444f",
  "block": 52733843,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-09T09:45:00",
  "op": [
    "transfer",
    {
      "from": "cmhate",
      "to": "huobi-pro",
      "amount": "1183.000 STEEM",
      "memo": "323402"
    }
  ]
}
cmhatebought 21.842 SBD for 185.255 STEEM from @cmhate
2021/04/09 09:43:18
current ownerdragonq
current orderid2771023773
current pays185.255 STEEM
open ownercmhate
open orderid1617961369
open pays21.842 SBD
Transaction InfoBlock #52733809/Trx 003154364748124b1331542a9e15c01f9e31f3bd
View Raw JSON Data
{
  "trx_id": "003154364748124b1331542a9e15c01f9e31f3bd",
  "block": 52733809,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 1,
  "timestamp": "2021-04-09T09:43:18",
  "op": [
    "fill_order",
    {
      "current_owner": "dragonq",
      "current_orderid": 2771023773,
      "current_pays": "185.255 STEEM",
      "open_owner": "cmhate",
      "open_orderid": 1617961369,
      "open_pays": "21.842 SBD"
    }
  ]
}
cmhateblockchain operation: limit order create
2021/04/09 09:43:12
ownercmhate
orderid1617961369
amount to sell103.110 SBD
min to receive874.540 STEEM
fill or killfalse
expiration2021-05-06T09:41:15
Transaction InfoBlock #52733807/Trx 2d06a0e6b32587281e3901b5b9853a5ee50ca4ea
View Raw JSON Data
{
  "trx_id": "2d06a0e6b32587281e3901b5b9853a5ee50ca4ea",
  "block": 52733807,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-09T09:43:12",
  "op": [
    "limit_order_create",
    {
      "owner": "cmhate",
      "orderid": 1617961369,
      "amount_to_sell": "103.110 SBD",
      "min_to_receive": "874.540 STEEM",
      "fill_or_kill": false,
      "expiration": "2021-05-06T09:41:15"
    }
  ]
}
cmhatebought 42.408 STEEM for 4.999 SBD from @uchiwa
2021/04/09 09:43:12
current ownercmhate
current orderid1617961369
current pays4.999 SBD
open owneruchiwa
open orderid1455997141
open pays42.408 STEEM
Transaction InfoBlock #52733807/Trx 2d06a0e6b32587281e3901b5b9853a5ee50ca4ea
View Raw JSON Data
{
  "trx_id": "2d06a0e6b32587281e3901b5b9853a5ee50ca4ea",
  "block": 52733807,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 4,
  "timestamp": "2021-04-09T09:43:12",
  "op": [
    "fill_order",
    {
      "current_owner": "cmhate",
      "current_orderid": 1617961369,
      "current_pays": "4.999 SBD",
      "open_owner": "uchiwa",
      "open_orderid": 1455997141,
      "open_pays": "42.408 STEEM"
    }
  ]
}
cmhatebought 597.726 STEEM for 70.425 SBD from @bnk
2021/04/09 09:43:12
current ownercmhate
current orderid1617961369
current pays70.425 SBD
open ownerbnk
open orderid407281
open pays597.726 STEEM
Transaction InfoBlock #52733807/Trx 2d06a0e6b32587281e3901b5b9853a5ee50ca4ea
View Raw JSON Data
{
  "trx_id": "2d06a0e6b32587281e3901b5b9853a5ee50ca4ea",
  "block": 52733807,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 3,
  "timestamp": "2021-04-09T09:43:12",
  "op": [
    "fill_order",
    {
      "current_owner": "cmhate",
      "current_orderid": 1617961369,
      "current_pays": "70.425 SBD",
      "open_owner": "bnk",
      "open_orderid": 407281,
      "open_pays": "597.726 STEEM"
    }
  ]
}
cmhatebought 8.480 STEEM for 0.999 SBD from @quicktrades
2021/04/09 09:43:12
current ownercmhate
current orderid1617961369
current pays0.999 SBD
open ownerquicktrades
open orderid1130406937
open pays8.480 STEEM
Transaction InfoBlock #52733807/Trx 2d06a0e6b32587281e3901b5b9853a5ee50ca4ea
View Raw JSON Data
{
  "trx_id": "2d06a0e6b32587281e3901b5b9853a5ee50ca4ea",
  "block": 52733807,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2021-04-09T09:43:12",
  "op": [
    "fill_order",
    {
      "current_owner": "cmhate",
      "current_orderid": 1617961369,
      "current_pays": "0.999 SBD",
      "open_owner": "quicktrades",
      "open_orderid": 1130406937,
      "open_pays": "8.480 STEEM"
    }
  ]
}
cmhatebought 41.130 STEEM for 4.845 SBD from @droida
2021/04/09 09:43:12
current ownercmhate
current orderid1617961369
current pays4.845 SBD
open ownerdroida
open orderid1543671703
open pays41.130 STEEM
Transaction InfoBlock #52733807/Trx 2d06a0e6b32587281e3901b5b9853a5ee50ca4ea
View Raw JSON Data
{
  "trx_id": "2d06a0e6b32587281e3901b5b9853a5ee50ca4ea",
  "block": 52733807,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 1,
  "timestamp": "2021-04-09T09:43:12",
  "op": [
    "fill_order",
    {
      "current_owner": "cmhate",
      "current_orderid": 1617961369,
      "current_pays": "4.845 SBD",
      "open_owner": "droida",
      "open_orderid": 1543671703,
      "open_pays": "41.130 STEEM"
    }
  ]
}
cmhateclaimed reward balance: 61.567 SBD, 81.236 SP
2021/04/07 12:47:27
accountcmhate
reward steem0.000 STEEM
reward sbd61.567 SBD
reward vests132285.555327 VESTS
Transaction InfoBlock #52680391/Trx dcb1f7a5f1d60c4d9704e53765c577dc1e563be1
View Raw JSON Data
{
  "trx_id": "dcb1f7a5f1d60c4d9704e53765c577dc1e563be1",
  "block": 52680391,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-07T12:47:27",
  "op": [
    "claim_reward_balance",
    {
      "account": "cmhate",
      "reward_steem": "0.000 STEEM",
      "reward_sbd": "61.567 SBD",
      "reward_vests": "132285.555327 VESTS"
    }
  ]
}
cmhatereceived 77.306 STEEM from power down installment (89.611 SP)
2021/04/05 03:09:57
from accountcmhate
to accountcmhate
withdrawn145923.588879 VESTS
deposited77.306 STEEM
Transaction InfoBlock #52611880/Virtual Operation #2
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 52611880,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2021-04-05T03:09:57",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "cmhate",
      "to_account": "cmhate",
      "withdrawn": "145923.588879 VESTS",
      "deposited": "77.306 STEEM"
    }
  ]
}
2021/04/04 23:23:27
voterg7terra
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight10000 (100.00%)
Transaction InfoBlock #52607395/Trx 6fff4e50082a8339b50a749d2576fa07287cf440
View Raw JSON Data
{
  "trx_id": "6fff4e50082a8339b50a749d2576fa07287cf440",
  "block": 52607395,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T23:23:27",
  "op": [
    "vote",
    {
      "voter": "g7terra",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 10000
    }
  ]
}
2021/04/04 19:29:48
voteralexcote
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight10000 (100.00%)
Transaction InfoBlock #52602766/Trx 86dac4920f5f98adc497042e148282ccebf976e8
View Raw JSON Data
{
  "trx_id": "86dac4920f5f98adc497042e148282ccebf976e8",
  "block": 52602766,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T19:29:48",
  "op": [
    "vote",
    {
      "voter": "alexcote",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 10000
    }
  ]
}
2021/04/04 16:59:42
voteresecholo
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight10000 (100.00%)
Transaction InfoBlock #52599792/Trx 7d44519b6c9e4d666d673dbcc03dbf2e8bb159ca
View Raw JSON Data
{
  "trx_id": "7d44519b6c9e4d666d673dbcc03dbf2e8bb159ca",
  "block": 52599792,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T16:59:42",
  "op": [
    "vote",
    {
      "voter": "esecholo",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 10000
    }
  ]
}
2021/04/04 15:30:06
voterdev.supporters
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight1000 (10.00%)
Transaction InfoBlock #52598016/Trx bb77889a3eaf7b0dc40d51f64dc7ea06c127fd7a
View Raw JSON Data
{
  "trx_id": "bb77889a3eaf7b0dc40d51f64dc7ea06c127fd7a",
  "block": 52598016,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:30:06",
  "op": [
    "vote",
    {
      "voter": "dev.supporters",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 1000
    }
  ]
}
2021/04/04 15:05:54
votermmmmkkkk311
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight10000 (100.00%)
Transaction InfoBlock #52597538/Trx dce5e9a5297d14814caaa99b6619916b8f2d7e3b
View Raw JSON Data
{
  "trx_id": "dce5e9a5297d14814caaa99b6619916b8f2d7e3b",
  "block": 52597538,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:05:54",
  "op": [
    "vote",
    {
      "voter": "mmmmkkkk311",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 10000
    }
  ]
}
2021/04/04 15:05:51
voterctime
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight1000 (10.00%)
Transaction InfoBlock #52597537/Trx 7df191edce6125464429dbc926892d7ed7a00d2f
View Raw JSON Data
{
  "trx_id": "7df191edce6125464429dbc926892d7ed7a00d2f",
  "block": 52597537,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:05:51",
  "op": [
    "vote",
    {
      "voter": "ctime",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 1000
    }
  ]
}
2021/04/04 15:05:45
voterdlike
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight600 (6.00%)
Transaction InfoBlock #52597535/Trx 908cade521ec7ed43d5293fa0d0cc44b8006dace
View Raw JSON Data
{
  "trx_id": "908cade521ec7ed43d5293fa0d0cc44b8006dace",
  "block": 52597535,
  "trx_in_block": 26,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:05:45",
  "op": [
    "vote",
    {
      "voter": "dlike",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 600
    }
  ]
}
2021/04/04 15:05:45
voteraccelerator
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight400 (4.00%)
Transaction InfoBlock #52597535/Trx 02a74032e4073ad1157b0e354f2626de363df2db
View Raw JSON Data
{
  "trx_id": "02a74032e4073ad1157b0e354f2626de363df2db",
  "block": 52597535,
  "trx_in_block": 25,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:05:45",
  "op": [
    "vote",
    {
      "voter": "accelerator",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 400
    }
  ]
}
2021/04/04 15:05:45
voterleo.voter
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight400 (4.00%)
Transaction InfoBlock #52597535/Trx e4544ee30143ac90fd71b7d512e08aa61dacbb37
View Raw JSON Data
{
  "trx_id": "e4544ee30143ac90fd71b7d512e08aa61dacbb37",
  "block": 52597535,
  "trx_in_block": 24,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:05:45",
  "op": [
    "vote",
    {
      "voter": "leo.voter",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 400
    }
  ]
}
2021/04/04 15:05:45
voterkhaleelkazi
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight400 (4.00%)
Transaction InfoBlock #52597535/Trx ec03b7606942d05993d5d75d855570ae023afab0
View Raw JSON Data
{
  "trx_id": "ec03b7606942d05993d5d75d855570ae023afab0",
  "block": 52597535,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:05:45",
  "op": [
    "vote",
    {
      "voter": "khaleelkazi",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 400
    }
  ]
}
2021/04/04 15:05:45
voterexyle
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight400 (4.00%)
Transaction InfoBlock #52597535/Trx 0059d2919e99d3b70d63f093efffe4886d54aa8c
View Raw JSON Data
{
  "trx_id": "0059d2919e99d3b70d63f093efffe4886d54aa8c",
  "block": 52597535,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:05:45",
  "op": [
    "vote",
    {
      "voter": "exyle",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 400
    }
  ]
}
2021/04/04 15:05:45
votersteem.leo
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight400 (4.00%)
Transaction InfoBlock #52597535/Trx bc7ba3424202b23489d1b444241b75ccbef8f2fe
View Raw JSON Data
{
  "trx_id": "bc7ba3424202b23489d1b444241b75ccbef8f2fe",
  "block": 52597535,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:05:45",
  "op": [
    "vote",
    {
      "voter": "steem.leo",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 400
    }
  ]
}
2021/04/04 15:05:45
voterezzy
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight400 (4.00%)
Transaction InfoBlock #52597535/Trx 3af523ea47c52cbb0ffd50bae0f65f7b82f2fd49
View Raw JSON Data
{
  "trx_id": "3af523ea47c52cbb0ffd50bae0f65f7b82f2fd49",
  "block": 52597535,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:05:45",
  "op": [
    "vote",
    {
      "voter": "ezzy",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 400
    }
  ]
}
2021/04/04 15:05:45
voternealmcspadden
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight400 (4.00%)
Transaction InfoBlock #52597535/Trx 278fa528f69d9aef4db732565c24ef0e99ee3c24
View Raw JSON Data
{
  "trx_id": "278fa528f69d9aef4db732565c24ef0e99ee3c24",
  "block": 52597535,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:05:45",
  "op": [
    "vote",
    {
      "voter": "nealmcspadden",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 400
    }
  ]
}
2021/04/04 15:05:45
votergerber
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight400 (4.00%)
Transaction InfoBlock #52597535/Trx df9d0d2ec4188d6e95b246b2074cca1354c8b300
View Raw JSON Data
{
  "trx_id": "df9d0d2ec4188d6e95b246b2074cca1354c8b300",
  "block": 52597535,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:05:45",
  "op": [
    "vote",
    {
      "voter": "gerber",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 400
    }
  ]
}
2021/04/04 15:04:45
voterbooming03
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight9900 (99.00%)
Transaction InfoBlock #52597515/Trx 08bc897f01d4a0765b47fd6abd97c1430118bc2a
View Raw JSON Data
{
  "trx_id": "08bc897f01d4a0765b47fd6abd97c1430118bc2a",
  "block": 52597515,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:04:45",
  "op": [
    "vote",
    {
      "voter": "booming03",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 9900
    }
  ]
}
2021/04/04 15:04:36
voterricardo306
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
weight1500 (15.00%)
Transaction InfoBlock #52597512/Trx c34e1526cb5770f27b5e24a191e6213f253a1cce
View Raw JSON Data
{
  "trx_id": "c34e1526cb5770f27b5e24a191e6213f253a1cce",
  "block": 52597512,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:04:36",
  "op": [
    "vote",
    {
      "voter": "ricardo306",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "weight": 1500
    }
  ]
}
2021/04/04 15:03:06
parent author
parent permlinkspark
authorcmhate
permlinkin-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems
titleIn-depth interpretation of spark VS Hadoop two big data analysis systems
body### Spark: fast and easy to use Spark is good at performance, but it is also known for its ease of use, because it comes with an easy-to-use API that supports Scala (native language), Java, Python, and Spark SQL. Spark SQL is very similar to SQL 92, so you can get started right away without any learning experience. Spark is a general-purpose parallel computing framework like Hadoop MapReduce open sourced by UC Berkeley AMP lab. Spark's distributed computing based on map reduce algorithm has the advantages of Hadoop MapReduce; but unlike MapReduce, the intermediate output results of Job can be saved. In memory, there is no need to read and write HDFS anymore, so Spark is better suited for algorithms that require iterative map reduce, such as data mining and machine learning. Spark also has an interactive mode, so that both developers and users can get immediate feedback on queries and other operations. MapReduce has no interactive mode, but with additional modules such as Hive and Pig, it is easier for adopters to use MapReduce. From the cost point of view: Spark requires a lot of memory, but a regular number of regular-speed disks can be used. Some users complained that temporary files will be generated and need to be cleaned up. These temporary files are usually kept for 7 days to speed up any processing on the same data set. Disk space is relatively cheap. Since Spark does not use disk input/input for processing, the used disk space can be used for SAN or NAS. Fault tolerance: Spark uses Resilient Distributed Data Sets (RDD), which are fault-tolerant collections in which data elements can perform parallel operations. RDD can reference data sets in external storage systems, such as shared file systems, HDFS, HBase, or any data source that provides Hadoop InputFormat. Spark can create RDDs from any storage source supported by Hadoop, including the local file system, or one of the file systems listed above. ### Hadoop: Distributed File System Hadoop is a project of http://Apache.org. It is actually a software library and framework for distributed processing of huge data sets (big data) across computer clusters using a simple programming model. Hadoop can be flexibly expanded. It can easily support from a single computer system to thousands of commercial systems that provide local storage and computing capabilities. In fact, Hadoop is the heavyweight big data platform in the field of big data analysis. Hadoop is composed of multiple modules that work together to build the Hadoop framework. The main modules of the Hadoop framework include the following: •Hadoop Common •Hadoop Distributed File System (HDFS) •Hadoop YARN •Hadoop MapReduce Although the above four modules form the core of Hadoop, there are several other modules. These modules include: Ambari, Avro, Cassandra, Hive, Pig, Oozie, Flume, and Sqoop. They further enhance and expand the functions of Hadoop, allowing it to be extended to the field of big data applications and process huge data sets. Many companies that use large data sets and analysis tools use Hadoop. It has become the de facto standard in big data application systems. The original intention of designing Hadoop was to handle this task: search and search billions of web pages, and collect this information into a database. It is precisely because of the desire to search and search the Internet that Hadoop's HDFS and distributed processing engine MapReduce are available. Cost: MapReduce uses a regular amount of memory. Because data processing is based on disks, companies have to buy faster disks and a lot of disk space to run MapReduce. MapReduce also needs more systems to distribute disk input/output to multiple systems. Fault tolerance: MapReduce uses TaskTracker nodes, which provide a heartbeat for JobTracker nodes. If there is no heartbeat, then the JobTracker node reschedules all the operations to be executed and ongoing operations to another TaskTracker node. This method is very effective in providing fault tolerance, but it will greatly extend the completion time of certain operations (even if there is only one failure). Summary: Spark and MapReduce have a symbiotic relationship. Hadoop provides features that Spark does not have, such as a distributed file system, while Spark provides real-time memory processing for those data sets that need it. The perfect big data scenario is exactly what the designers had envisioned: let Hadoop and Spark run together in the same team. ![image.png](https://cdn.steemitimages.com/DQmTSMj71mfjN2jQikHxBNvcfwjkzKqh67b3TJd27BDhCR9/image.png)
json metadata{"tags":["spark","hadoop"],"image":["https://cdn.steemitimages.com/DQmTSMj71mfjN2jQikHxBNvcfwjkzKqh67b3TJd27BDhCR9/image.png"],"links":["http://Apache.org"],"app":"steemit/0.2","format":"markdown"}
Transaction InfoBlock #52597482/Trx 7cbc9f79f434f61cedf803d4dc9a3d9d0130f42e
View Raw JSON Data
{
  "trx_id": "7cbc9f79f434f61cedf803d4dc9a3d9d0130f42e",
  "block": 52597482,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-04T15:03:06",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "spark",
      "author": "cmhate",
      "permlink": "in-depth-interpretation-of-spark-vs-hadoop-two-big-data-analysis-systems",
      "title": "In-depth interpretation of spark VS Hadoop two big data analysis systems",
      "body": "### Spark: fast and easy to use\nSpark is good at performance, but it is also known for its ease of use, because it comes with an easy-to-use API that supports Scala (native language), Java, Python, and Spark SQL. Spark SQL is very similar to SQL 92, so you can get started right away without any learning experience.\n\nSpark is a general-purpose parallel computing framework like Hadoop MapReduce open sourced by UC Berkeley AMP lab. Spark's distributed computing based on map reduce algorithm has the advantages of Hadoop MapReduce; but unlike MapReduce, the intermediate output results of Job can be saved. In memory, there is no need to read and write HDFS anymore, so Spark is better suited for algorithms that require iterative map reduce, such as data mining and machine learning.\n\nSpark also has an interactive mode, so that both developers and users can get immediate feedback on queries and other operations. MapReduce has no interactive mode, but with additional modules such as Hive and Pig, it is easier for adopters to use MapReduce.\n\nFrom the cost point of view: Spark requires a lot of memory, but a regular number of regular-speed disks can be used. Some users complained that temporary files will be generated and need to be cleaned up. These temporary files are usually kept for 7 days to speed up any processing on the same data set. Disk space is relatively cheap. Since Spark does not use disk input/input for processing, the used disk space can be used for SAN or NAS.\n\nFault tolerance: Spark uses Resilient Distributed Data Sets (RDD), which are fault-tolerant collections in which data elements can perform parallel operations. RDD can reference data sets in external storage systems, such as shared file systems, HDFS, HBase, or any data source that provides Hadoop InputFormat. Spark can create RDDs from any storage source supported by Hadoop, including the local file system, or one of the file systems listed above.\n\n### Hadoop: Distributed File System\n\nHadoop is a project of http://Apache.org. It is actually a software library and framework for distributed processing of huge data sets (big data) across computer clusters using a simple programming model. Hadoop can be flexibly expanded. It can easily support from a single computer system to thousands of commercial systems that provide local storage and computing capabilities. In fact, Hadoop is the heavyweight big data platform in the field of big data analysis.\n\nHadoop is composed of multiple modules that work together to build the Hadoop framework. The main modules of the Hadoop framework include the following:\n\n•Hadoop Common\n\n•Hadoop Distributed File System (HDFS)\n\n•Hadoop YARN\n\n•Hadoop MapReduce\n\nAlthough the above four modules form the core of Hadoop, there are several other modules. These modules include: Ambari, Avro, Cassandra, Hive, Pig, Oozie, Flume, and Sqoop. They further enhance and expand the functions of Hadoop, allowing it to be extended to the field of big data applications and process huge data sets.\n\nMany companies that use large data sets and analysis tools use Hadoop. It has become the de facto standard in big data application systems. The original intention of designing Hadoop was to handle this task: search and search billions of web pages, and collect this information into a database. It is precisely because of the desire to search and search the Internet that Hadoop's HDFS and distributed processing engine MapReduce are available.\n\nCost: MapReduce uses a regular amount of memory. Because data processing is based on disks, companies have to buy faster disks and a lot of disk space to run MapReduce. MapReduce also needs more systems to distribute disk input/output to multiple systems.\n\nFault tolerance: MapReduce uses TaskTracker nodes, which provide a heartbeat for JobTracker nodes. If there is no heartbeat, then the JobTracker node reschedules all the operations to be executed and ongoing operations to another TaskTracker node. This method is very effective in providing fault tolerance, but it will greatly extend the completion time of certain operations (even if there is only one failure).\n\nSummary: Spark and MapReduce have a symbiotic relationship. Hadoop provides features that Spark does not have, such as a distributed file system, while Spark provides real-time memory processing for those data sets that need it. The perfect big data scenario is exactly what the designers had envisioned: let Hadoop and Spark run together in the same team.\n\n\n\n![image.png](https://cdn.steemitimages.com/DQmTSMj71mfjN2jQikHxBNvcfwjkzKqh67b3TJd27BDhCR9/image.png)",
      "json_metadata": "{\"tags\":[\"spark\",\"hadoop\"],\"image\":[\"https://cdn.steemitimages.com/DQmTSMj71mfjN2jQikHxBNvcfwjkzKqh67b3TJd27BDhCR9/image.png\"],\"links\":[\"http://Apache.org\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
    }
  ]
}
cmhatereceived 26.605 SBD, 26.641 SP author reward for @cmhate / simple-reading-of-polkadot
2021/04/03 14:10:27
authorcmhate
permlinksimple-reading-of-polkadot
sbd payout26.605 SBD
steem payout0.000 STEEM
vesting payout43382.044148 VESTS
Transaction InfoBlock #52567923/Virtual Operation #18
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 52567923,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 18,
  "timestamp": "2021-04-03T14:10:27",
  "op": [
    "author_reward",
    {
      "author": "cmhate",
      "permlink": "simple-reading-of-polkadot",
      "sbd_payout": "26.605 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "43382.044148 VESTS"
    }
  ]
}
2021/04/02 20:07:09
voteralexcote
authorcmhate
permlinkthe-value-path-of-big-data
weight10000 (100.00%)
Transaction InfoBlock #52546474/Trx b1318c2cda6a8bf5cc9056a66154c285b6416067
View Raw JSON Data
{
  "trx_id": "b1318c2cda6a8bf5cc9056a66154c285b6416067",
  "block": 52546474,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T20:07:09",
  "op": [
    "vote",
    {
      "voter": "alexcote",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 10000
    }
  ]
}
2021/04/02 17:43:21
votermeedo
authorcmhate
permlinkthe-value-path-of-big-data
weight10000 (100.00%)
Transaction InfoBlock #52543624/Trx bd568df1ff415050b6097eb08f3846685e34dd24
View Raw JSON Data
{
  "trx_id": "bd568df1ff415050b6097eb08f3846685e34dd24",
  "block": 52543624,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T17:43:21",
  "op": [
    "vote",
    {
      "voter": "meedo",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 10000
    }
  ]
}
2021/04/02 16:53:27
voterlyon89
authorcmhate
permlinkthe-value-path-of-big-data
weight10000 (100.00%)
Transaction InfoBlock #52542635/Trx 7622288340242784ce5a85bd134ebab21a263e7f
View Raw JSON Data
{
  "trx_id": "7622288340242784ce5a85bd134ebab21a263e7f",
  "block": 52542635,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T16:53:27",
  "op": [
    "vote",
    {
      "voter": "lyon89",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 10000
    }
  ]
}
2021/04/02 15:14:21
voterbluesniper
authorcmhate
permlinkthe-value-path-of-big-data
weight10000 (100.00%)
Transaction InfoBlock #52540674/Trx 39e71ea75c2537c4ce570f5d34c3ab061333737e
View Raw JSON Data
{
  "trx_id": "39e71ea75c2537c4ce570f5d34c3ab061333737e",
  "block": 52540674,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T15:14:21",
  "op": [
    "vote",
    {
      "voter": "bluesniper",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 10000
    }
  ]
}
2021/04/02 13:50:06
voterdev.supporters
authorcmhate
permlinkthe-value-path-of-big-data
weight1000 (10.00%)
Transaction InfoBlock #52539001/Trx f53c9f70e54b6097c3d435eaefea856dc36f46e6
View Raw JSON Data
{
  "trx_id": "f53c9f70e54b6097c3d435eaefea856dc36f46e6",
  "block": 52539001,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:50:06",
  "op": [
    "vote",
    {
      "voter": "dev.supporters",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 1000
    }
  ]
}
2021/04/02 13:42:39
votercpt-sparrow
authorcmhate
permlinkthe-value-path-of-big-data
weight500 (5.00%)
Transaction InfoBlock #52538852/Trx 0fd9553a0f32fdd230df85b65654207c349437ef
View Raw JSON Data
{
  "trx_id": "0fd9553a0f32fdd230df85b65654207c349437ef",
  "block": 52538852,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:42:39",
  "op": [
    "vote",
    {
      "voter": "cpt-sparrow",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 500
    }
  ]
}
2021/04/02 13:42:27
votermmmmkkkk311
authorcmhate
permlinkthe-value-path-of-big-data
weight10000 (100.00%)
Transaction InfoBlock #52538848/Trx 3d24259a96861425028d5321fe3476c74b3c397b
View Raw JSON Data
{
  "trx_id": "3d24259a96861425028d5321fe3476c74b3c397b",
  "block": 52538848,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:42:27",
  "op": [
    "vote",
    {
      "voter": "mmmmkkkk311",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 10000
    }
  ]
}
2021/04/02 13:42:27
voterctime
authorcmhate
permlinkthe-value-path-of-big-data
weight10000 (100.00%)
Transaction InfoBlock #52538848/Trx 9fa0351f2f7743e07ccfa5635eb56e74656748fe
View Raw JSON Data
{
  "trx_id": "9fa0351f2f7743e07ccfa5635eb56e74656748fe",
  "block": 52538848,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:42:27",
  "op": [
    "vote",
    {
      "voter": "ctime",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 10000
    }
  ]
}
2021/04/02 13:42:24
voterdlike
authorcmhate
permlinkthe-value-path-of-big-data
weight600 (6.00%)
Transaction InfoBlock #52538847/Trx b1a0f96872750728d7018303d4245ddde83b4816
View Raw JSON Data
{
  "trx_id": "b1a0f96872750728d7018303d4245ddde83b4816",
  "block": 52538847,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:42:24",
  "op": [
    "vote",
    {
      "voter": "dlike",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 600
    }
  ]
}
2021/04/02 13:42:24
voteraccelerator
authorcmhate
permlinkthe-value-path-of-big-data
weight500 (5.00%)
Transaction InfoBlock #52538847/Trx 6f826a17d17bf68ced4edbe896280f4ff9861736
View Raw JSON Data
{
  "trx_id": "6f826a17d17bf68ced4edbe896280f4ff9861736",
  "block": 52538847,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:42:24",
  "op": [
    "vote",
    {
      "voter": "accelerator",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 500
    }
  ]
}
2021/04/02 13:42:24
voterleo.voter
authorcmhate
permlinkthe-value-path-of-big-data
weight500 (5.00%)
Transaction InfoBlock #52538847/Trx 89727352212e9410e5e627f0a1648cbb92e30499
View Raw JSON Data
{
  "trx_id": "89727352212e9410e5e627f0a1648cbb92e30499",
  "block": 52538847,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:42:24",
  "op": [
    "vote",
    {
      "voter": "leo.voter",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 500
    }
  ]
}
2021/04/02 13:42:24
voterkhaleelkazi
authorcmhate
permlinkthe-value-path-of-big-data
weight500 (5.00%)
Transaction InfoBlock #52538847/Trx 9cdb8adbaaec0634325babc1e6787b6f0c50e724
View Raw JSON Data
{
  "trx_id": "9cdb8adbaaec0634325babc1e6787b6f0c50e724",
  "block": 52538847,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:42:24",
  "op": [
    "vote",
    {
      "voter": "khaleelkazi",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 500
    }
  ]
}
2021/04/02 13:42:24
votersteem.leo
authorcmhate
permlinkthe-value-path-of-big-data
weight500 (5.00%)
Transaction InfoBlock #52538847/Trx fe70c90c135173f5128890494455e0440e9fbe12
View Raw JSON Data
{
  "trx_id": "fe70c90c135173f5128890494455e0440e9fbe12",
  "block": 52538847,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:42:24",
  "op": [
    "vote",
    {
      "voter": "steem.leo",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 500
    }
  ]
}
2021/04/02 13:42:24
voterezzy
authorcmhate
permlinkthe-value-path-of-big-data
weight500 (5.00%)
Transaction InfoBlock #52538847/Trx 61148749a17e1bc05e931cb3773daa09bb5cc9d9
View Raw JSON Data
{
  "trx_id": "61148749a17e1bc05e931cb3773daa09bb5cc9d9",
  "block": 52538847,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:42:24",
  "op": [
    "vote",
    {
      "voter": "ezzy",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 500
    }
  ]
}
2021/04/02 13:42:24
voterexyle
authorcmhate
permlinkthe-value-path-of-big-data
weight500 (5.00%)
Transaction InfoBlock #52538847/Trx 9b761b13be6d74d6419ebe01ba14b6c1f0403d8a
View Raw JSON Data
{
  "trx_id": "9b761b13be6d74d6419ebe01ba14b6c1f0403d8a",
  "block": 52538847,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:42:24",
  "op": [
    "vote",
    {
      "voter": "exyle",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 500
    }
  ]
}
2021/04/02 13:42:24
voternealmcspadden
authorcmhate
permlinkthe-value-path-of-big-data
weight500 (5.00%)
Transaction InfoBlock #52538847/Trx 8ca2ad35315c31003f40a9e17eda13498da587fe
View Raw JSON Data
{
  "trx_id": "8ca2ad35315c31003f40a9e17eda13498da587fe",
  "block": 52538847,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:42:24",
  "op": [
    "vote",
    {
      "voter": "nealmcspadden",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 500
    }
  ]
}
2021/04/02 13:42:21
votergerber
authorcmhate
permlinkthe-value-path-of-big-data
weight500 (5.00%)
Transaction InfoBlock #52538846/Trx b8824cb65d5cb9be1d92fd6459718419ad86385d
View Raw JSON Data
{
  "trx_id": "b8824cb65d5cb9be1d92fd6459718419ad86385d",
  "block": 52538846,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:42:21",
  "op": [
    "vote",
    {
      "voter": "gerber",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 500
    }
  ]
}
2021/04/02 13:41:33
voterinfo4all
authorcmhate
permlinkthe-value-path-of-big-data
weight10000 (100.00%)
Transaction InfoBlock #52538830/Trx bb51dd2af8347413948d1d83876bc96c454ce07b
View Raw JSON Data
{
  "trx_id": "bb51dd2af8347413948d1d83876bc96c454ce07b",
  "block": 52538830,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:41:33",
  "op": [
    "vote",
    {
      "voter": "info4all",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 10000
    }
  ]
}
2021/04/02 13:39:57
voterbooming03
authorcmhate
permlinkthe-value-path-of-big-data
weight9900 (99.00%)
Transaction InfoBlock #52538799/Trx 90390781479ef47dfa199612f7bbe3d3ed0a2a2d
View Raw JSON Data
{
  "trx_id": "90390781479ef47dfa199612f7bbe3d3ed0a2a2d",
  "block": 52538799,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:39:57",
  "op": [
    "vote",
    {
      "voter": "booming03",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "weight": 9900
    }
  ]
}
cmhatepublished a new post: the-value-path-of-big-data
2021/04/02 13:39:21
parent author
parent permlinkbig
authorcmhate
permlinkthe-value-path-of-big-data
titleThe value path of big data
body### The 4V of big data is not on the same level Speaking of big data, the first impression is that the 4V proposed in the book "Big Data Era", massive data volume (volume), fast data flow and dynamic data system (velocity), diverse data types (variety) ) And huge data value (value). The first three Vs directly describe the characteristics of the data itself. Numerous companies in the big data industry have introduced various storage and data processing solutions to deal with the technical challenges brought about by big data. The early gold prospectors made a lot of money. A large number of computer rooms full of data are left. But what about good value? ### The last V is not ideal. Take Palantir, the most famous company in the industry, as an example. His founder is the famous Silicon Valley investment and entrepreneurial godfather, paypal founder Peter Thiel. Its first and largest customer is the CIA, which assists in the fight against terrorism. It is said that relying on their assistance, the CIA found Bin Laden's trace. Palantir became famous for this. Its latest round of financing is USD 450 million, and the company is valued at USD 20 billion. It is a startup company second only to uber, airbnb and Xiaomi. But some recent news broke a series of Palantir's problems. Last year, at least three important customers terminated their contracts, including Coca-Cola, America Express, and Nasdaq. On the one hand, these customers complained that the company charges too high, which can be as high as $1 million per month, which is far from worth it. Moreover, the cooperation between the client and the company's young engineers is a headache. Palantir last announced that its "book value" for the entire year of last year was US$1.7 billion, but in fact the final revenue was only US$450 million. The reservation value is the cost that the customer may have to pay, including many trial periods, and the contract value of free users. The huge gap between these two data shows that very few customers turn out to be paying users. Palantir's situation just shows that it is not easy to obtain the huge data value of big data. There is indeed a lot of value hidden in big data, but the realization of value does not lie in the data analysis itself, but in the collision of data and business scenarios. ### Several problems faced in Palantir's data practice: The value of data is closely related to industry scenarios. Palantir is good at catching bad guys. Through a large number of data associations, it discovers abnormalities in the business, and then realizes the value of data through abnormal control. Such scenarios are more suitable in security, finance and other fields. When extended to other scenes, the effect is often unsatisfactory. The involvement of in-depth industry scenarios often requires in-depth involvement in the industry, which is costly and has a long cycle. The data and analysts themselves are also costs, the cost of acquiring big data, the high cost of data scientists, the opportunity cost of failure in analytical work, and the degree to which the value of data is reflected. These all have a direct impact on big data projects. Whether these cost-to-value ratios can be controlled within a certain range, and in the long run, whether there is a linear decrease in cost is also a key factor in corporate decision-making. The skills and thinking abilities of engineers, the training and retention of data scientists are not easy, the training of young engineers, the learning curve and cost are all points that need to be considered. ### Several milestones on the road to data value Gartner has a very simple and clear data analysis and difficulty division model, which defines four levels from the difficulty of data analysis to the realization of data value. The definition of these four levels is also very suitable to be regarded as the four milestones in our data value exploration. Descriptive, the analysis to solve what happened, is a relatively simple analysis. Descriptive analysis usually requires the precipitation of big data into smaller, higher-value information, through aggregation to provide insights and reports on an event that has occurred. Diagnostics, on the basis of event data description, provides in-depth analysis of the cause, usually requires more dimensional data, longer data span, and discovers the relationship between events and data through correlation analysis. Predictive (Predictive), predictive analysis through a series of statistics, modeling, data mining and machine learning techniques to learn recent and historical data, to help analysts make certain predictions about the future. Prescriptive, prescriptive analysis breaks through the analysis and extends to the execution stage. It combines prediction, deployment, rules, multiple predictions, scoring, execution and optimization rules, and finally forms a closed-loop decision management capability. Past practice has shown that more than 75% of data analysis scenarios are descriptive analysis. Most of the data warehouses and BI systems that have been established by enterprises can be attributed to this scenario. Daily operation reports, operational dashboards, cockpits, etc. belong to this scenario. The realization of this kind of application. Diagnostic and predictive analysis applications are more used in specific scenarios such as recommendation and operational abnormality analysis. The scope of use is small and the effects are uneven. The standard analysis scenario directly opens up analysis and execution, which is currently mainly reflected in more specific business scenarios such as autonomous driving and robots. In a business environment, the value of data requires more than just analysis. The real value is obtained through business decision-making and business execution after data analysis. The author uses the following picture to depict the value path of data. The more to the right, the higher the business value index reflected by the data, and the higher the business value reflected. The light green and dark green parts in the figure are a large number of manual participation processes, which help further manual processing and processing of the previous data analysis process and results. In the IT-led era in the past, these two parts were often undertaken by the IT department, driven by business needs, and the implementation effect was not good, and they were often criticized by the business department. In the era of big data, business departments are deeply involved and gradually become the main users and innovators of data. Through data analysis, business personnel interpret, enrich, judge, make decisions, and finally complete the closed loop of execution to realize the value of data. As a leading practitioner of the value of big data, TalkingData has set up its own capability map based on this idea: In the course of several years of development, it has realized the accumulation of massive data; statistical analysis, operational analysis, and advertising monitoring, A series of DMP tool platforms further realize the technical realization of description, diagnosis, and predictive analysis; The innovatively established professional data consulting team provides personal services to core customers, assists companies in making business decisions using big data, and escorts the company's big data innovation; In the past year, TalkingData is gradually building an open data ecosystem to bring more extensive data value to customers. ![image.png](https://cdn.steemitimages.com/DQmQZFUF4raZvoKpD8TZMqBWYrgBvC21bJtZxPFvQ5beptG/image.png)
json metadata{"tags":["big","data"],"image":["https://cdn.steemitimages.com/DQmQZFUF4raZvoKpD8TZMqBWYrgBvC21bJtZxPFvQ5beptG/image.png"],"app":"steemit/0.2","format":"markdown"}
Transaction InfoBlock #52538787/Trx c694bd074aedafe1b122515635ff8c24225e92e2
View Raw JSON Data
{
  "trx_id": "c694bd074aedafe1b122515635ff8c24225e92e2",
  "block": 52538787,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-02T13:39:21",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "big",
      "author": "cmhate",
      "permlink": "the-value-path-of-big-data",
      "title": "The value path of big data",
      "body": "### The 4V of big data is not on the same level\n\nSpeaking of big data, the first impression is that the 4V proposed in the book \"Big Data Era\", massive data volume (volume), fast data flow and dynamic data system (velocity), diverse data types (variety) ) And huge data value (value).\n\nThe first three Vs directly describe the characteristics of the data itself. Numerous companies in the big data industry have introduced various storage and data processing solutions to deal with the technical challenges brought about by big data. The early gold prospectors made a lot of money. A large number of computer rooms full of data are left. But what about good value?\n\n### The last V is not ideal.\n\nTake Palantir, the most famous company in the industry, as an example. His founder is the famous Silicon Valley investment and entrepreneurial godfather, paypal founder Peter Thiel. Its first and largest customer is the CIA, which assists in the fight against terrorism. It is said that relying on their assistance, the CIA found Bin Laden's trace. Palantir became famous for this. Its latest round of financing is USD 450 million, and the company is valued at USD 20 billion. It is a startup company second only to uber, airbnb and Xiaomi.\n\nBut some recent news broke a series of Palantir's problems. Last year, at least three important customers terminated their contracts, including Coca-Cola, America Express, and Nasdaq. On the one hand, these customers complained that the company charges too high, which can be as high as $1 million per month, which is far from worth it. Moreover, the cooperation between the client and the company's young engineers is a headache.\n\nPalantir last announced that its \"book value\" for the entire year of last year was US$1.7 billion, but in fact the final revenue was only US$450 million. The reservation value is the cost that the customer may have to pay, including many trial periods, and the contract value of free users. The huge gap between these two data shows that very few customers turn out to be paying users.\n\nPalantir's situation just shows that it is not easy to obtain the huge data value of big data.\n\nThere is indeed a lot of value hidden in big data, but the realization of value does not lie in the data analysis itself, but in the collision of data and business scenarios.\n\n### Several problems faced in Palantir's data practice:\n\nThe value of data is closely related to industry scenarios. Palantir is good at catching bad guys. Through a large number of data associations, it discovers abnormalities in the business, and then realizes the value of data through abnormal control. Such scenarios are more suitable in security, finance and other fields. When extended to other scenes, the effect is often unsatisfactory. The involvement of in-depth industry scenarios often requires in-depth involvement in the industry, which is costly and has a long cycle.\nThe data and analysts themselves are also costs, the cost of acquiring big data, the high cost of data scientists, the opportunity cost of failure in analytical work, and the degree to which the value of data is reflected. These all have a direct impact on big data projects. Whether these cost-to-value ratios can be controlled within a certain range, and in the long run, whether there is a linear decrease in cost is also a key factor in corporate decision-making.\nThe skills and thinking abilities of engineers, the training and retention of data scientists are not easy, the training of young engineers, the learning curve and cost are all points that need to be considered.\n\n### Several milestones on the road to data value\n\nGartner has a very simple and clear data analysis and difficulty division model, which defines four levels from the difficulty of data analysis to the realization of data value. The definition of these four levels is also very suitable to be regarded as the four milestones in our data value exploration.\n\nDescriptive, the analysis to solve what happened, is a relatively simple analysis. Descriptive analysis usually requires the precipitation of big data into smaller, higher-value information, through aggregation to provide insights and reports on an event that has occurred.\nDiagnostics, on the basis of event data description, provides in-depth analysis of the cause, usually requires more dimensional data, longer data span, and discovers the relationship between events and data through correlation analysis.\n\n\nPredictive (Predictive), predictive analysis through a series of statistics, modeling, data mining and machine learning techniques to learn recent and historical data, to help analysts make certain predictions about the future.\n\nPrescriptive, prescriptive analysis breaks through the analysis and extends to the execution stage. It combines prediction, deployment, rules, multiple predictions, scoring, execution and optimization rules, and finally forms a closed-loop decision management capability.\n\nPast practice has shown that more than 75% of data analysis scenarios are descriptive analysis. Most of the data warehouses and BI systems that have been established by enterprises can be attributed to this scenario. Daily operation reports, operational dashboards, cockpits, etc. belong to this scenario. The realization of this kind of application. Diagnostic and predictive analysis applications are more used in specific scenarios such as recommendation and operational abnormality analysis. The scope of use is small and the effects are uneven. The standard analysis scenario directly opens up analysis and execution, which is currently mainly reflected in more specific business scenarios such as autonomous driving and robots. In a business environment, the value of data requires more than just analysis. The real value is obtained through business decision-making and business execution after data analysis.\n\nThe author uses the following picture to depict the value path of data. The more to the right, the higher the business value index reflected by the data, and the higher the business value reflected.\n\n\nThe light green and dark green parts in the figure are a large number of manual participation processes, which help further manual processing and processing of the previous data analysis process and results. In the IT-led era in the past, these two parts were often undertaken by the IT department, driven by business needs, and the implementation effect was not good, and they were often criticized by the business department. In the era of big data, business departments are deeply involved and gradually become the main users and innovators of data. Through data analysis, business personnel interpret, enrich, judge, make decisions, and finally complete the closed loop of execution to realize the value of data.\n\nAs a leading practitioner of the value of big data, TalkingData has set up its own capability map based on this idea: In the course of several years of development, it has realized the accumulation of massive data; statistical analysis, operational analysis, and advertising monitoring, A series of DMP tool platforms further realize the technical realization of description, diagnosis, and predictive analysis; The innovatively established professional data consulting team provides personal services to core customers, assists companies in making business decisions using big data, and escorts the company's big data innovation; In the past year, TalkingData is gradually building an open data ecosystem to bring more extensive data value to customers.\n\n\n![image.png](https://cdn.steemitimages.com/DQmQZFUF4raZvoKpD8TZMqBWYrgBvC21bJtZxPFvQ5beptG/image.png)",
      "json_metadata": "{\"tags\":[\"big\",\"data\"],\"image\":[\"https://cdn.steemitimages.com/DQmQZFUF4raZvoKpD8TZMqBWYrgBvC21bJtZxPFvQ5beptG/image.png\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
    }
  ]
}
cmhatereceived 17.840 SBD, 26.774 SP author reward for @cmhate / sashimi-dex-and-new-revelations
2021/03/30 15:20:57
authorcmhate
permlinksashimi-dex-and-new-revelations
sbd payout17.840 SBD
steem payout0.000 STEEM
vesting payout43598.255299 VESTS
Transaction InfoBlock #52455259/Virtual Operation #16
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 52455259,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 16,
  "timestamp": "2021-03-30T15:20:57",
  "op": [
    "author_reward",
    {
      "author": "cmhate",
      "permlink": "sashimi-dex-and-new-revelations",
      "sbd_payout": "17.840 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "43598.255299 VESTS"
    }
  ]
}
cmhatereceived 17.122 SBD, 27.822 SP author reward for @cmhate / kp3r-serve-for-unsmart-smart-contracts
2021/03/29 13:39:39
authorcmhate
permlinkkp3r-serve-for-unsmart-smart-contracts
sbd payout17.122 SBD
steem payout0.000 STEEM
vesting payout45305.255880 VESTS
Transaction InfoBlock #52424729/Virtual Operation #12
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 52424729,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 12,
  "timestamp": "2021-03-29T13:39:39",
  "op": [
    "author_reward",
    {
      "author": "cmhate",
      "permlink": "kp3r-serve-for-unsmart-smart-contracts",
      "sbd_payout": "17.122 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "45305.255880 VESTS"
    }
  ]
}
2021/03/29 07:40:45
voterwowmiko
authorcmhate
permlinksashimi-dex-and-new-revelations
weight10000 (100.00%)
Transaction InfoBlock #52417644/Trx 8578e3d0debd671935a530f2072350c78ff85ae9
View Raw JSON Data
{
  "trx_id": "8578e3d0debd671935a530f2072350c78ff85ae9",
  "block": 52417644,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-03-29T07:40:45",
  "op": [
    "vote",
    {
      "voter": "wowmiko",
      "author": "cmhate",
      "permlink": "sashimi-dex-and-new-revelations",
      "weight": 10000
    }
  ]
}
cmhatereceived 77.249 STEEM from power down installment (89.611 SP)
2021/03/29 03:09:57
from accountcmhate
to accountcmhate
withdrawn145923.588879 VESTS
deposited77.249 STEEM
Transaction InfoBlock #52412281/Virtual Operation #3
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 52412281,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 3,
  "timestamp": "2021-03-29T03:09:57",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "cmhate",
      "to_account": "cmhate",
      "withdrawn": "145923.588879 VESTS",
      "deposited": "77.249 STEEM"
    }
  ]
}
2021/03/27 15:04:45
voterrycharde
authorcmhate
permlinksimple-reading-of-polkadot
weight10000 (100.00%)
Transaction InfoBlock #52369425/Trx 4c5b208cc4ce0a09de6b22efb1a218b458f19abd
View Raw JSON Data
{
  "trx_id": "4c5b208cc4ce0a09de6b22efb1a218b458f19abd",
  "block": 52369425,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-03-27T15:04:45",
  "op": [
    "vote",
    {
      "voter": "rycharde",
      "author": "cmhate",
      "permlink": "simple-reading-of-polkadot",
      "weight": 10000
    }
  ]
}
2021/03/27 15:00:06
voterdev.supporters
authorcmhate
permlinksimple-reading-of-polkadot
weight1000 (10.00%)
Transaction InfoBlock #52369333/Trx bef6c3b4922aa2cc0c1e78d433289a9f6e0099c6
View Raw JSON Data
{
  "trx_id": "bef6c3b4922aa2cc0c1e78d433289a9f6e0099c6",
  "block": 52369333,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-03-27T15:00:06",
  "op": [
    "vote",
    {
      "voter": "dev.supporters",
      "author": "cmhate",
      "permlink": "simple-reading-of-polkadot",
      "weight": 1000
    }
  ]
}
2021/03/27 14:23:03
voterharaldsylwester
authorcmhate
permlinksimple-reading-of-polkadot
weight10000 (100.00%)
Transaction InfoBlock #52368599/Trx 25d98bd3844a7ff218c23dbc09fb42aa7531e8aa
View Raw JSON Data
{
  "trx_id": "25d98bd3844a7ff218c23dbc09fb42aa7531e8aa",
  "block": 52368599,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-03-27T14:23:03",
  "op": [
    "vote",
    {
      "voter": "haraldsylwester",
      "author": "cmhate",
      "permlink": "simple-reading-of-polkadot",
      "weight": 10000
    }
  ]
}
2021/03/27 14:15:54
voterjuneuniverse
authorcmhate
permlinksimple-reading-of-polkadot
weight10000 (100.00%)
Transaction InfoBlock #52368457/Trx 657eba730cd03ae303c7306e1373ed9aee875a6c
View Raw JSON Data
{
  "trx_id": "657eba730cd03ae303c7306e1373ed9aee875a6c",
  "block": 52368457,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-03-27T14:15:54",
  "op": [
    "vote",
    {
      "voter": "juneuniverse",
      "author": "cmhate",
      "permlink": "simple-reading-of-polkadot",
      "weight": 10000
    }
  ]
}
2021/03/27 14:13:45
voterdeathwing
authorcmhate
permlinksimple-reading-of-polkadot
weight6000 (60.00%)
Transaction InfoBlock #52368415/Trx 922f06497cc15fe07ebe28b50656b237e5059cef
View Raw JSON Data
{
  "trx_id": "922f06497cc15fe07ebe28b50656b237e5059cef",
  "block": 52368415,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-03-27T14:13:45",
  "op": [
    "vote",
    {
      "voter": "deathwing",
      "author": "cmhate",
      "permlink": "simple-reading-of-polkadot",
      "weight": 6000
    }
  ]
}
2021/03/27 14:13:39
voterdlike
authorcmhate
permlinksimple-reading-of-polkadot
weight600 (6.00%)
Transaction InfoBlock #52368413/Trx 29a9d64eaa3566cadcda8a04f758b211a5991e75
View Raw JSON Data
{
  "trx_id": "29a9d64eaa3566cadcda8a04f758b211a5991e75",
  "block": 52368413,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-03-27T14:13:39",
  "op": [
    "vote",
    {
      "voter": "dlike",
      "author": "cmhate",
      "permlink": "simple-reading-of-polkadot",
      "weight": 600
    }
  ]
}
2021/03/27 14:13:39
voteraccelerator
authorcmhate
permlinksimple-reading-of-polkadot
weight2400 (24.00%)
Transaction InfoBlock #52368413/Trx c2d200dec7cb2eb226ed2d328394a6d1bc96c1eb
View Raw JSON Data
{
  "trx_id": "c2d200dec7cb2eb226ed2d328394a6d1bc96c1eb",
  "block": 52368413,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-03-27T14:13:39",
  "op": [
    "vote",
    {
      "voter": "accelerator",
      "author": "cmhate",
      "permlink": "simple-reading-of-polkadot",
      "weight": 2400
    }
  ]
}
2021/03/27 14:13:39
voterkhaleelkazi
authorcmhate
permlinksimple-reading-of-polkadot
weight2400 (24.00%)
Transaction InfoBlock #52368413/Trx 3906eea7500c9c300542c3c44028b8686cc60ca7
View Raw JSON Data
{
  "trx_id": "3906eea7500c9c300542c3c44028b8686cc60ca7",
  "block": 52368413,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-03-27T14:13:39",
  "op": [
    "vote",
    {
      "voter": "khaleelkazi",
      "author": "cmhate",
      "permlink": "simple-reading-of-polkadot",
      "weight": 2400
    }
  ]
}

Account Metadata

POSTING JSON METADATA
None
JSON METADATA
None
{
  "posting_json_metadata": {},
  "json_metadata": {}
}

Auth Keys

Owner
Single Signature
Public Keys
STM5sy5sD49nEwAAucKGZqGQzUpFa5DH7AYMSvS3j4t81EPHcKbHM1/1
Active
Single Signature
Public Keys
STM55mYp7tMkJpKdrVFhFB11actS5nUk8PUwka8vF9ZsAoER36Cir1/1
Posting
Single Signature
Public Keys
STM7s1dgt4yLwe6QLAzpQwYjjXoZkEvYfVcGJjkDARaPRSFv7BeFh1/1
Memo
STM7M32PsYg9AeBnrcYMwddhZUtaC7D2QVf85bqUy6Uc2mEm7hZfQ
{
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM5sy5sD49nEwAAucKGZqGQzUpFa5DH7AYMSvS3j4t81EPHcKbHM",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM55mYp7tMkJpKdrVFhFB11actS5nUk8PUwka8vF9ZsAoER36Cir",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7s1dgt4yLwe6QLAzpQwYjjXoZkEvYfVcGJjkDARaPRSFv7BeFh",
        1
      ]
    ]
  },
  "memo": "STM7M32PsYg9AeBnrcYMwddhZUtaC7D2QVf85bqUy6Uc2mEm7hZfQ"
}

Witness Votes

0 / 30
No active witness votes.
[]