Michael Lee McClure, 26, from Billings, Montana, on 23 April 2021
Victim Info
- Michael Lee McClure
- Black/African American
- 26
- Male
Details
After a nine-hour standoff, deputies broke into a residence around 11 p.m. and found Michael Lee McClure in the attic. He reportedly charged at the officers, then ran away. Gunfire reportedly was exchanged, and McClure was killed. Officers reportedly used multiple methods to try to flush the man out, including chemical agents, robots and drones.Primary Evidence & Links
Additional Evidence
- Michael Lee McClure
- 26
- Male
- African-American/Black
- African-American/Black
- Not imputed
- 4000 block Ridgewood Lane South
- Billings
- MT
- 59106
- Yellowstone
- 4000 block Ridgewood Lane South Billings MT 59106 Yellowstone
- Yellowstone County Sheriff's Office
- Pending investigation
- https://fatalencounters.org/wp-content/uploads/2021/05/Michael-Lee-McClure.jpg
Source
Source ID: 30093 - Fatal Encounters
Cross References
This report has possible entries from multiple sources
- Mapping Police Violence -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 64776. Submitted in Mainchain Tx CDBA9770D2047A883D0BC25CCB93C75B05B1D54E8BA3C777B74B3A591091A2CD, at block height 139110
Transaction details
Tx CDBA9770D2047A883D0BC25CCB93C75B05B1D54E8BA3C777B74B3A591091A2CD
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: 1WJZgImAf8eDqDLgb/B0esTJf/XOZ8CrbtG2EVRQCSJZBJRFHvoPPfdIAJ83xaN8Q3g5wcnQnPj22qcmGMofDw==
Raw Tx data:
Hash Comparison
Hash stored in database: 33a9658a4ba18f453cda3542d6362c2931ffa71a25dd1f57313b7e84ef357dd3
Hash from Mainchain Tx: 33a9658a4ba18f453cda3542d6362c2931ffa71a25dd1f57313b7e84ef357dd3
Dynamically generated hash: 364f4faded83172c7d0fe8078e77c4d3404f057cbfa67b0d9893f7296e33a11c
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: