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,936,408


44 transactions in this block, produced at 2020-03-24 17:41:21 (UTC)

c29a5092 Steem Monsters entered into match queue
cb7060a2 Steem Monsters submitted a team for battle
a0f106dd Steem Monsters claimed quest reward
08bcc2f4 Steem Monsters claimed quest reward
481d58ef Steem Monsters entered into match queue
a7e70914 Steem Monsters entered into match queue
2091f002 Steem Monsters entered into match queue
dd3144c0 custom json
required_auths[]
required_posting_auths
0.uraniumfuture
idnextcolony
json"{"username":"uraniumfuture","type":"deploy","command":{"tr_var1":{"corvette": 1},"tr_var2":1476,"tr_var3":1028,"tr_var4":10,"tr_var5":2,"tr_var6":5,"tr_var7":2,"tr_var8":"P-Z6BF4QG7M40"}}"
7e69d689 Steem Monsters revealed their cards for battle
61ec845f Steem Monsters entered into match queue
bdd0ddd9 Steem Monsters submitted a team for battle
d155d96b Steem Monsters revealed their cards for battle
3537c309 Steem Monsters submitted a team for battle
75dae4c5 Steem Monsters submitted a team for battle

Show raw block data


1 virtual op in this block.

virtual producer reward: 0.252 SP

Show raw virtual op data