Michael Lee McClure, 26, from Billings, Montana, on 23 April 2021
Victim Info
- Michael Lee McClure
- Black/African American
- 26
- Male
Details
Yellowstone County deputies attempted to pull over a van because of a traffic violation, but the driver evaded the stop. A few hours after the incident, Laurel Police officers responded to a report of a suspicious vehcile, the same van from the prior stop. A man was outside of the van and eventually got back into the vehicle and drove away. Another chase ensued. The van eventually crashed into a neighborhood and two individuals exited the van and ran away. Police allege they noticed one of the people had a gun and the pair were attempting to break into a home. Police took one of the individuals into custody, and a standoff began with the other. The other individual got into a home and was allegedly hiding in the attic. Police entered the home and claim the individual charged at them before they shot and killed them.Primary Evidence & Links
Additional Evidence
- Michael Lee McClure
- 26
- Male
- Black
- 4000 Ridgewood Lane South
- Billings
- MT
- 59106
- Yellowstone
- Yellowstone County Sheriff's Office
- MT0560000
- Gunshot
- Pending investigation
- No known charges
- No
- Allegedly Armed
- gun
- attack
- other
- no
- 6805
- Suburban
- https://fatalencounters.org/wp-content/uploads/2021/05/Michael-Lee-McClure.jpg
- Traffic Stop
- traffic violation
Source
Source ID: 9161 - Mapping Police Violence
Cross References
This report has possible entries from multiple sources
- Fatal Encounters -Michael Lee McClure, 26, from Billings, Montana, on 23 April 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 64771. Submitted in Mainchain Tx F1B3EB214E2AD2C5623F46C4981FA402F7DD3B7B3C8542E47588E8AE2A193D26, at block height 139105
Transaction details
Tx F1B3EB214E2AD2C5623F46C4981FA402F7DD3B7B3C8542E47588E8AE2A193D26
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: aI/sf3hw3E4Z63Rrg5VfzowTlhwpsGeoNzI34c6PRLkGjIQjrPTXqk8CxbxEfXOvp/yhcoRwC6TjeRa1ErztTw==
Raw Tx data:
Hash Comparison
Hash stored in database: 1a5356c814eb690702f73460b13f135fef778b1149a39736273fdaf1d0d96570
Hash from Mainchain Tx: 1a5356c814eb690702f73460b13f135fef778b1149a39736273fdaf1d0d96570
Dynamically generated hash: 1a5356c814eb690702f73460b13f135fef778b1149a39736273fdaf1d0d96570
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: