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,870,208


48 transactions in this block, produced at 2020-03-22 09:45:18 (UTC)

d29bc1b1 Steem Monsters submitted a team for battle
6394a95e Steem Monsters submitted a team for battle
cae1d39e Steem Monsters submitted a team for battle
f26f01c3 Steem Monsters entered into match queue
424dec4e Steem Monsters entered into match queue
ef3bb766 custom json
required_auths[]
required_posting_auths
0.swedishdragon76
idsm_tournament_checkin
json{"tournament_id":"8a3cdabead48e51f36af41e07bdb2d91bfbfd983","app":"steemmonsters/0.7.14"}
8623117e Steem Monsters entered into match queue
272cfe10 comment options: 100.0% SBD, allow votes: true, allow curation rewards: true
fbab1a94 custom json
required_auths[]
required_posting_auths
0.kreur
idsm_enter_tournament
json{"tournament_id":"8a3cdabead48e51f36af41e07bdb2d91bfbfd983","signed_pw":null,"app":"steemmonsters/0.7.14"}
93ffd5fd Steem Monsters entered into match queue
eea977c2 Steem Monsters submitted a team for battle
7fbaf0e5 Steem Monsters submitted a team for battle
83e3ba12 Steem Monsters entered into match queue
ac726bed Steem Monsters entered into match queue

Show raw block data


1 virtual op in this block.

virtual producer reward: 0.248 SP

Show raw virtual op data