Roderick Inge, 29, from Tuscaloosa, Alabama, on 15 April 2021
Victim Info
- Roderick Inge
- Black/African American
- 29
- Male
Details
Officers responded to report of a domestic dispute involving a man who authorities say shot into a vehicle carrying his two children, ages 3 and 5, and their mother. As officers were speaking with the victim, police said they observed Roderick Inge driving in the area and chased him. After a short car chase, Inge ditched his vehicle in a parking lot and ran into a wooded area. He was found in a wooded area, and allegedly produced and fired a handgun as officers approached. The officers shot and killed him.Primary Evidence & Links
Additional Evidence
- Roderick Inge
- 29
- Male
- Black
- 100 Skyland Blvd.
- Tuscaloosa
- AL
- 35405
- Tuscaloosa
- Tuscaloosa Police Department
- AL0630100
- Gunshot
- Pending investigation
- No known charges
- No
- Allegedly armed
- gun
- attack
- foot
- Suburban
- https://fatalencounters.org/wp-content/uploads/2021/04/Roderick-Inge.jpg
- Part 1 Violent Crime/Domestic Disturbance (intimate partner)
- shooting/domestic disturbance
Source
Source ID: 9190 - Mapping Police Violence
Cross References
This report has possible entries from multiple sources
- Fatal Encounters -Roderick Inge, 29, from Tuscaloosa, Alabama, on 15 April 2021
- Washington Post -Roderick Inge, 29, from Tuscaloosa, Alabama - shot on 15 April 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 64884. Submitted in Mainchain Tx 9AA3D037A5C9AF5277A32E1D72B91244FABF7EDAC2D782F5E97853F06C711584, at block height 139218
Transaction details
Tx 9AA3D037A5C9AF5277A32E1D72B91244FABF7EDAC2D782F5E97853F06C711584
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: Y5HZ7sLPl5rmzfuv3K/ijZECxfyekMiE/fpFXy40mnhThze+mSAhSyJiLXyxCqpJhi6G2cU7d3wOWemo6JkqUA==
Raw Tx data:
Hash Comparison
Hash stored in database: 25b9718526339ba922bed1e4779d6f8b4507c1379786ffdf1748f804e2a48855
Hash from Mainchain Tx: 25b9718526339ba922bed1e4779d6f8b4507c1379786ffdf1748f804e2a48855
Dynamically generated hash: ada495a6752ffe763763a8de4b018cc88e412e6003a8872043a657b32834c378
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: