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,021,708


12 transactions in this block, produced at 2020-03-27 17:40:48 (UTC)

5612b14c custom json
required_auths
0.mmshop
required_posting_auths[]
idssc-mainnet1
json"{"contractName":"tokens","contractAction":"transfer","contractPayload":{"symbol":"UNTAMED","to":"shoemanchu","quantity":"4","memo":"You have successfully bought 4 UNTAMED."}}"
9ffd79a4 Steem Monsters entered into match queue
09ea51be custom json
required_auths[]
required_posting_auths
0.schlafhacking
idnextcolony
json{"type":"buildship","command":{"tr_var2":"corvette","tr_var1":"P-ZQ00NXI5JOG"},"username":"schlafhacking"}
24df4c2e custom json
required_auths[]
required_posting_auths
0.raycoms
idnextcolony
json{"username":"raycoms","type":"buildship","command":{"tr_var1":"P-ZWOKIXJ6MO0","tr_var2":"destroyer"}}
188b0522 Steem Monsters entered into match queue
964f2702 Steem Monsters entered into match queue
7eecc0f0 Steem Monsters entered into match queue
0788d9a5 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