Lorenzo Aguilar, 37, from Deming, New Mexico, on 24 November 2020
Victim Info
- Lorenzo Aguilar
- Unknown
- 37
- Male
Details
At 12:47 p.m., police were notified regarding Lorenzo Aguilar, who was known to have a felony arrest warrant. Aguilar was reported to be on Birch Street in Deming. When officers arrived, they saw Aguilar in a vehicle. As officers approached the vehicle, Aguilar fled and police pursued. Officers pursed Aguilar at speeds exceeding 100 mph within the city of Deming. Aguilar crashed into a wall at the corner of Pine and Zinc streets. Aguilar ran south on Zinc. An officer chased Aguilar behind a house on Spruce Street. A second officer arrived, and Aguilar allegedly shot at the officers, who shot and killed him.Primary Evidence & Links
Additional Evidence
- Lorenzo Aguilar
- 37
- Male
- Unknown race
- W. Spruce St. and S. Zinc St.
- Deming
- NM
- 88030
- Luna
- Deming Police Department
- Gunshot
- Pending investigation
- No known charges
- No
- gun
- attack
- Car
- No
- 6335
- Rural
Source
Source ID: 8646 - Mapping Police Violence
Cross References
This report has possible entries from multiple sources
- Washington Post -Lorenzo Aguilar, 37, from Deming, New Mexico - shot on 24 November 2020
- Fatal Encounters -Lorenzo Aguilar, 37, from Deming, New Mexico, on 24 November 2020
- Killed By Police -Lorenzo Aguilar, 37, from New Mexico on 24 November 2020
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 66641. Submitted in Mainchain Tx B9D745AC953AF6B801AD73F612EAB1719AF845EBCAA726766512E6FCDEACB212, at block height 143268
Transaction details
Tx B9D745AC953AF6B801AD73F612EAB1719AF845EBCAA726766512E6FCDEACB212
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: LxmmVz7/afRmMsaTaCYmO5lIJky7W/pBmFaUbL2jLxshPTqsuXqT/sqpVzwEE9bv1yE33003stq9taLePWWVOA==
Raw Tx data:
Hash Comparison
Hash stored in database: 8efc4a7c0b475f8afe302900e4506939acd132be3860d8789ea1f3b1a645de63
Hash from Mainchain Tx: 8efc4a7c0b475f8afe302900e4506939acd132be3860d8789ea1f3b1a645de63
Dynamically generated hash: de3dd141cd8a800f336c96e689b788bd782c01f7ca8110e00603d719ca3f5531
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: