Kevin L. Duncan, 38, from Bellefontaine, Ohio, on 20 March 2021
Victim Info
- Kevin L. Duncan
- Black/African American
- 38
- Male
Details
Officers pulled over a man and told him to get out of the vehicle. An officer reportedly got hurt in a fight. When backup officers arrived, they found the man exhibiting aggressive behavior. Officers sicced a dog on him, and after he was restrained he reportedly started having a medical emergency. Multiple doses of Narcan were not successful, and he died.Primary Evidence & Links
Additional Evidence
- Kevin L. Duncan
- 38
- Male
- African-American/Black
- African-American/Black
- Not imputed
- 500 block East High Avenue
- Bellefontaine
- OH
- 43311
- Logan
- 500 block East High Avenue Bellefontaine OH 43311 Logan
- Bellefontaine Police Department
- Pending investigation
- https://fatalencounters.org/wp-content/uploads/2021/04/Kevin-L.-Duncan.jpeg
Source
Source ID: 29856 - Fatal Encounters
Cross References
This report has possible entries from multiple sources
- Mapping Police Violence -Kevin L. Duncan, 38, from Bellefontaine, Ohio, on 20 March 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65270. Submitted in Mainchain Tx 425F967F88AAA798DA80C3F9BE133818D460F320E5C2690D524F9E79C9A21C83, at block height 140369
Transaction details
Tx 425F967F88AAA798DA80C3F9BE133818D460F320E5C2690D524F9E79C9A21C83
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: YeLVdBEoX37gCIjjOj9zeFUHEKEMzQDNsxhQH6Wm5nU4syG2No5MDeVBq4AKZ3EAu5YJtMgH1tawSiWRdBFn6g==
Raw Tx data:
Hash Comparison
Hash stored in database: c28418e3bc5dca88f5c79dd081deab7cac844311f65b50bea0e9506117f591f6
Hash from Mainchain Tx: c28418e3bc5dca88f5c79dd081deab7cac844311f65b50bea0e9506117f591f6
Dynamically generated hash: 7df65311bef89e1db0dafb928ffa43a65b9bbb6be4ab4341fa7f049748894be8
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: