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,140,940


27 transactions in this block, produced at 2020-03-31 22:24:54 (UTC)

ffbdfcd8 Steem Monsters submitted a team for battle
626ce8a6 Steem Monsters combine cards
3ba3e3e5 custom json
required_auths[]
required_posting_auths
0.xul
idnextcolony
json{"username":"xul","type":"buildship","command":{"tr_var1":"P-Z2ITJYBYRZK","tr_var2":"explorership"}}
5a9ed2af Steem Monsters entered into match queue
a744ebc8 Steem Monsters submitted a team for battle
d4c53fdb custom json
required_auths[]
required_posting_auths
0.steemnet
idnextcolony
json"{"username": "steemnet", "type":"explorespace","command":{"tr_var1":"P-ZE0OD35PZY8","tr_var2":-640,"tr_var3":-488, "tr_var4":"explorership"}}"
5104630c Steem Monsters entered into match queue
87273a5d Steem Monsters entered into match queue
1836a11e Steem Monsters entered into match queue
b6202ea7 Steem Monsters submitted a team for battle
5fd192c0 Steem Monsters submitted a team for battle
3b6200c3 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