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 41,974,483


21 transactions in this block, produced at 2020-03-26 01:50:18 (UTC)

d500cfa0 custom json
required_auths[]
required_posting_auths
0.joebabana
idnextcolony
json{"username":"joebabana","type":"upgrade","command":{"tr_var1":"P-ZKZ4HRN5WKG","tr_var2":"coppermine"}}
c7206550 custom json
required_auths[]
required_posting_auths
0.joebabana
idnextcolony
json{"type":"buildship","command":{"tr_var1":"P-ZT5U4U85W34","tr_var2":"explorership"}}
4b46a420 Steem Monsters entered into match queue
215874f8 Steem Monsters submitted a team for battle
6b6676a7 Steem Monsters started a daily quest
bfdb54a5 Steem Monsters entered into match queue
ecdd6b16 Steem Monsters revealed their cards for battle
6f57aabf Steem Monsters revealed their cards for battle
ac44f4c3 Steem Monsters entered into match queue
a13555ce Steem Monsters entered into match queue
f4255bd7 Steem Monsters entered into match queue
7c471379 Steem Monsters entered into match queue
298b70b2 Steem Monsters submitted a team for battle
7edfc79c Steem Monsters entered into match queue

Show raw block data


1 virtual op in this block.

virtual producer reward: 0.251 SP

Show raw virtual op data