Warning: Steem witnesses executed a hard fork on 2020-05-20, seizing 23.6M STEEM from 65 accounts. The funds were transferred to an account named @community321, the ownership (and intentions) of which have not been revealed. The witnesses claim to have been targeting accounts which defended against a hostile takeover in early March, but at least 2 accounts on the list have been inactive for over 4 years.

Coverage:
- Decrypt.io: Steem network to seize $5 million from its own users
- SteemPeak.com: Official Announcement by @softfork22888
- GitHub.com: view steemd HF23 changes

What you can do:
- Send exchanges a notice of the pending class action lawsuit.
- Switch to HIVE, the community-led fork. Visit Hive.blog and Hiveblocks.com.

Prev | Next Block 42,141,408


19 transactions in this block, produced at 2020-03-31 22:48:30 (UTC)

632e29ae custom json
required_auths[]
required_posting_auths
0.mrspointm
idnotify
json["setLastRead",{"date":"2020-03-31T22:48:23"}]
be3635b5 Steem Monsters started a daily quest
154a4fab Steem Monsters submitted a team for battle
d4a763ce Steem Monsters submitted a team for battle
56d72d03 Steem Monsters submitted a team for battle
c08cd80f comment options: max payout 0 SBD, 100.0% SBD, allow votes: true, allow curation rewards: true
387177f1 custom json
required_auths[]
required_posting_auths
0.tiger-zaps
idnextcolony
json{"username":"tiger-zaps","type":"explorespace","command":{"tr_var1":"P-ZX1UH6KSM40","tr_var2":848,"tr_var3":57,"tr_var4":"explorership"}}
ce5c248d Steem Monsters entered into match queue
88b0132e Steem Monsters submitted a team for battle
4991226f custom json
required_auths[]
required_posting_auths
0.afrog
idnextcolony
json{"username":"afrog","type":"upgrade","command":{"tr_var1":"P-ZIAN5CY4S00","tr_var2":"uraniummine"}}
cc302d9e Steem Monsters submitted a team for battle

Show raw block data


1 virtual op in this block.

virtual producer reward: 0.251 SP

Show raw virtual op data