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
- Race unspecified
- NA
- NA
- W Spruce St & S Zinc St
- Deming
- NM
- 88030
- Luna
- W Spruce St & S Zinc St Deming NM 88030 Luna
- Deming Police Department
- Gunshot
- Pending investigation
Source
Source ID: 29225 - Fatal Encounters
Cross References
This report has possible entries from multiple sources
- Washington Post -Lorenzo Aguilar, 37, from Deming, New Mexico - shot on 24 November 2020
- Mapping Police Violence -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 66642. Submitted in Mainchain Tx E95A62FC8D0566B95DC88DAC2BAAF14D62ABF5A2767BB34A4F0C98EC33BF165E, at block height 143269
Transaction details
Tx E95A62FC8D0566B95DC88DAC2BAAF14D62ABF5A2767BB34A4F0C98EC33BF165E
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: rBQmF49ewu+ydon05XdCuoAkzow1O/lltViOFiR01xs76zyrkol8bric3wC4GS86+SKEIfcoa5F1L0GL9QNUUw==
Raw Tx data:
Hash Comparison
Hash stored in database: f5bf8bb0cacce8a08fa28310d7e0034e127cba7884c72e9620d7d0903e2c5d84
Hash from Mainchain Tx: f5bf8bb0cacce8a08fa28310d7e0034e127cba7884c72e9620d7d0903e2c5d84
Dynamically generated hash: f5bf8bb0cacce8a08fa28310d7e0034e127cba7884c72e9620d7d0903e2c5d84
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: