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,981,202


26 transactions in this block, produced at 2020-03-26 07:30:24 (UTC)

6d9da7fd wants 127.661 SBD for 546.638 STEEM (show details)
ownerunipsycho
orderid1,585,207,821
amount_to_sell546.638 STEEM
min_to_receive127.661 SBD
fill_or_killfalse
expiration2020-04-22 07:25:08
cabd9a20 Steem Monsters entered into match queue
0cdb9c09 Steem Monsters entered into match queue
a43ba132 custom json
required_auths[]
required_posting_auths
0.witnesstools
idscot_claim_token
json[{"symbol":"NEOXAG"}]
117b924b Steem Monsters submitted a team for battle
f8ee55d6 Steem Monsters entered into match queue
dfacc9ab Steem Monsters entered into match queue
b658315f custom json
required_auths[]
required_posting_auths
0.honeybeerbear
idscot_claim_token
json{"symbol":"IV"}
1fb3e8c7 Steem Monsters entered into match queue
e7a2d358 Steem Monsters submitted a team for battle
18f9fd6c Steem Monsters entered into match queue
7b2a9fae Steem Monsters submitted a team for battle
e91cb744 Steem Monsters entered into match queue
e1b56657 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