Sergio Gutierrez Chairez, 31, from Dexter, New Mexico, on 21 March 2021
Victim Info
- Sergio Gutierrez Chairez
- Hispanic/Latino
- 31
- Male
Details
Sergio Gutierrez Chairez was shot and killed while barricaded inside a semi-truck parked on his property. Deputies had gone to the address at 7:19 p.m. to serve Chairez with two outstanding arrest warrants. When they arrived deputies saw Chairez outside, but were unable to enter the premises because it was fenced off and had a locked gate. After obtaining a search warrant, deputies entered the property, and Chairez barricaded himself inside a semi-truck. Deputies eventually entered the semi-truck, and a deputy shot and killed Chairez.Primary Evidence & Links
Additional Evidence
- Sergio Gutierrez Chairez
- 31
- Male
- Hispanic/Latino
- Hispanic/Latino
- Not imputed
- 6400 Shadow Road
- Dexter
- NM
- 88230
- Chaves
- 6400 Shadow Road Dexter NM 88230 Chaves
- Chaves County Sheriff's Office
- Pending investigation
- https://fatalencounters.org/wp-content/uploads/2021/04/Sergio-Gutierrez-Chairez.jpg
Source
Source ID: 29868 - Fatal Encounters
Cross References
This report has possible entries from multiple sources
- Mapping Police Violence -Sergio Gutierrez Chairez, 31, from Dexter, New Mexico, on 21 March 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65252. Submitted in Mainchain Tx B3627AFDCAC4CD12905A0241ABF25BEE8607C8767F7FC2D0487D0A8CB2D3DF64, at block height 140351
Transaction details
Tx B3627AFDCAC4CD12905A0241ABF25BEE8607C8767F7FC2D0487D0A8CB2D3DF64
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: HSJkfKPmaRf2M4v2BYdaiAlf4Yx9bLHQ3zDP0f6WxqVqP3pspfDxV/I5aXDoxr6J/XGup57Wfm7QU5kFA2OXqg==
Raw Tx data:
Hash Comparison
Hash stored in database: 9da53432dabea89bdfb40f6e58df6f291875f26511d1e7c005eb676d0c4dbf0e
Hash from Mainchain Tx: 9da53432dabea89bdfb40f6e58df6f291875f26511d1e7c005eb676d0c4dbf0e
Dynamically generated hash: 9498317d631933e619e9d3feea4081d9c1627115f5651695cc5b31a98a2ddd8c
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: