Roger Dale Keller, 71, from Calera, Alabama, on 31 May 2021
Victim Info
- Roger Dale Keller
- White/European American
- 71
- Male
Details
Officers responded to a call of a man threatening to shoot two people in the front yard of a residence around 11:30 a.m. Police were told that the man fired multiple shots before offices arrived. Upon arrival, an officer saw the man standing in the yard with a gun. As the officer got out of their vehicle, gunfire was exchanged, and Roger Keller was shot and killed.Primary Evidence & Links
Additional Evidence
- Roger Dale Keller
- 71
- Male
- European-American/White
- European-American/White
- Not imputed
- 60 Co Rd 954
- Calera
- AL
- 35040
- Chilton
- 60 Co Rd 954 Calera AL 35040 Chilton
- Jemison Police Department
- Pending investigation
- https://fatalencounters.org/wp-content/uploads/2021/06/Roger-Dale-Keller.jpg
Source
Source ID: 30335 - Fatal Encounters
Cross References
This report has possible entries from multiple sources
- Washington Post -Roger Dale Keller, 71, from Jemison, Alabama - shot on 31 May 2021
- Mapping Police Violence -Roger Dale Keller, 71, from Jemison, Alabama, on 31 May 2021
- Mapping Police Violence -Roger Dale Keller, 71, from Jemison, Alabama, on 31 May 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 64372. Submitted in Mainchain Tx 1762261DA811597ACCAE1FC1396D7F1D909B3B474C7DF15F555D798D2743404F, at block height 137942
Transaction details
Tx 1762261DA811597ACCAE1FC1396D7F1D909B3B474C7DF15F555D798D2743404F
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: FTlX20YhN/+YbzPjW/pyATr2u+LyYdHfqglo2G/7bKsxLacAXu/v4vR3Cq5jm2jFdC0Nv+cYTxl8FqgKX7ppwA==
Raw Tx data:
Hash Comparison
Hash stored in database: 52a3286878c92de879bbe20a0c6ff446d3c0bca35ccda1e1dc42cc3c4793e4fa
Hash from Mainchain Tx: 52a3286878c92de879bbe20a0c6ff446d3c0bca35ccda1e1dc42cc3c4793e4fa
Dynamically generated hash: 48f203fefb2c43e25941dc0180273a57a1033ec438b289e62072918919e0ac06
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: