Shawn Michael Evanuk, 48, from Centerville, Georgia, on 20 March 2021
Victim Info
- Shawn Michael Evanuk
- Unknown
- 48
- Male
Details
Police responded to a domestic dispute call. When officers arrived, they met Shawn Michael Evanuk in the driveway of the home. Evanuk seemed to be upset and went into the residence where he barricaded himself along with his three children. Deputies responded, and Evanuk released the two of the children. Evanuk allegedly was threatening to harm to the 2-year-old and to burn the house down with them in it. Deputies entered the house and made contact with Evanuk who was armed with a knife. A struggle took place and Evanuk was shot and killed by a deputy.Primary Evidence & Links
Additional Evidence
- Shawn Michael Evanuk
- 48
- Male
- Race unspecified
- NA
- NA
- 305 Village Walk
- Centerville
- GA
- 31028
- Houston
- 305 Village Walk Centerville GA 31028 Houston
- Houston County Sheriff's Office
- Pending investigation
Source
Source ID: 29860 - Fatal Encounters
Cross References
This report has possible entries from multiple sources
- Washington Post -Shawn Michael Evanuk, 48, from Centerville, Georgia - shot on 20 March 2021
- Mapping Police Violence -Shawn Michael Evanuk, 48, from Centerville, Georgia, on 20 March 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65266. Submitted in Mainchain Tx 968048881AB4001C3D0C6352636235D2196F396EB3F369D736839DAE0B4E89A6, at block height 140365
Transaction details
Tx 968048881AB4001C3D0C6352636235D2196F396EB3F369D736839DAE0B4E89A6
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: sp813yWfvhbp42shK39BvDNGgi6oCZBUHvQS06e201UQu+mVAwsQnCYgnpGvYzbgB5dr9iVto7Xbj150IG4Ukw==
Raw Tx data:
Hash Comparison
Hash stored in database: 13833b3c23b6c88264bbcc47e60b9e0a29085e5e30a211bae70d3b5765c777f2
Hash from Mainchain Tx: 13833b3c23b6c88264bbcc47e60b9e0a29085e5e30a211bae70d3b5765c777f2
Dynamically generated hash: 4b38de0c0036dfbc7663d3e75e4bc71dcc60a78c8b62a4596cf388781bffbe1a
Hashes Match?How is the comparison calculated?
The hash stored in the database is used as the identifier for this report, and can be seen in the URL. The hash from the Mainchain Tx is the hash sent to and stored on Mainchain. Finally, the "generated hash" is generated each time this page is loaded, using the same data used for the hash submitted to Mainchain.
Raw data used to generate the hash, using the Node.js crypto.createHash('sha256') algorithm: