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,042,136


30 transactions in this block, produced at 2020-03-28 10:56:36 (UTC)

c6fa28f3 Steem Monsters entered into match queue
3a2ab1b7 custom json
required_auths[]
required_posting_auths
0.captain.kirk
idnextcolony
json{"type":"buildship","command":{"tr_var2":"frigate","tr_var1":"P-Z714ZROLTO0"},"username":"captain.kirk"}
01243589 Steem Monsters submitted a team for battle
9ed8f4a7 custom json
required_auths[]
required_posting_auths
0.allanbeh
idsm_open_all
json{"edition":4,"qty":2,"app":"steemmonsters/0.7.14"}
dd085792 Steem Monsters submitted a team for battle
19202e8a custom json
required_auths[]
required_posting_auths
0.mistersunshine
idnextcolony
json{"username":"mistersunshine","type":"upgradeyamato","command":{"tr_var1":"P-ZKEBJQW8IG0","tr_var2":"yamato"}}
b5221bd7 Steem Monsters entered into match queue
ff5449f2 Steem Monsters entered into match queue
dffd3fde Steem Monsters entered into match queue
10a3774c Steem Monsters list cards for sale on the market
98655d72 Steem Monsters entered into match queue
7e82c320 Steem Monsters entered into match queue
1d7c1655 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