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,982,582


31 transactions in this block, produced at 2020-03-26 08:40:15 (UTC)

4c8cab2a Steem Monsters submitted a team for battle
5b0794cb transfer 0.100 STEEM to {"id":"ssc-mainnet1","json":{"contractName":"steempegged","contractAction":"removeWithdrawal","contractPayload":{"id":"14b039fc37723cafcce9c5ec5931cf09f814a90e-fee"}}}
17067121 Steem Monsters entered into match queue
2000f405 Steem Monsters entered into match queue
6cecd286 Steem Monsters submitted a team for battle
bba5f7a3 Steem Monsters submitted a team for battle
2a40b8d6 custom json
required_auths[]
required_posting_auths
0.uraniumfuture
idnextcolony
json"{"username": "uraniumfuture", "type":"attack","command":{"tr_var1":{"corvette":{"pos":1,"n":217}},"tr_var2":109,"tr_var3":437,"tr_var4":"P-ZC1WQYMXR1S"}}"
542566ba Steem Monsters submitted a team for battle
0b96c260 Steem Monsters submitted a team for battle
68b9802b Steem Monsters entered into match queue
0e4c702b 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