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,984,684


40 transactions in this block, produced at 2020-03-26 10:26:39 (UTC)

4e7400d9 Steem Monsters submitted a team for battle
41f78061 custom json
required_auths[]
required_posting_auths
0.bowess
idhb_create_shopitems
json{"client_id":"bgnq7wh58"}
0628bd02 Steem Monsters revealed their cards for battle
a48768aa Steem Monsters submitted a team for battle
c5c8faf4 Steem Monsters entered into match queue
1cc6d48e claim reward: 0.098 STEEM and 0.099 SP
829dad70 comment options: 100.0% SBD, allow votes: true, allow curation rewards: true
f559631b Steem Monsters submitted a team for battle
93783114 custom json
required_auths
0.brooklyn-nets
required_posting_auths[]
idssc-mainnet1
json{"contractName":"tokens","contractAction":"transfer","contractPayload":{"symbol":"STEEMP","to":"new-jersey","quantity":"19.2","memo":""}}
7dcdc425 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