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,039,864


20 transactions in this block, produced at 2020-03-28 09:01:15 (UTC)

6e104742 custom json
required_auths
0.freepressturkey
required_posting_auths[]
idssc-mainnet1
json{"contractName":"tokens","contractAction":"stake","contractPayload":{"to":"freepressturkey","symbol":"PAL","quantity":"0.188"}}
d461e684 Steem Monsters submitted a team for battle
fc03ce0d Steem Monsters entered into match queue
2343a202 Steem Monsters submitted a team for battle
eaaae9b4 custom json
required_auths[]
required_posting_auths
0.jeenger
idscot_claim_token
json{"symbol":"MARLIANS"}
00c4378d Steem Monsters entered into match queue
26ce6297 Steem Monsters entered into match queue
6ee840ee Steem Monsters started a daily quest
547ac937 Steem Monsters entered into match queue
786704d5 Steem Monsters entered into match queue
68479de2 Steem Monsters entered into match queue
1cda7673 Steem Monsters entered into match queue
0b4e19bd Steem Monsters submitted a team for battle
d5c4b9af 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