Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Riverside, Ohio

Kevlin Wallace, 39, from Riverside, Ohio, on 27 July 2021

Victim Info

  • Kevlin Wallace
  • Black/African American
  • 39
  • Male

Details

In a 911 call, a woman said a man had broke into her home and had her boyfriend, daughter, and the child's grandfather held hostage inside their home. The caller also reported the man had a gun held to their heads. An officer and Kevlin Wallace exchanged gunfire. Police said neither were hit by the gunfire. Wallace ran and police converged on the area they thought Wallace was hiding when a single gunshot was heard. Wallace was found suffering from a single fatal gunshot wound to his head.

Additional Evidence

  • Kevlin Wallace
  • 39
  • Male
  • African-American/Black
  • African-American/Black
  • Not imputed
  • 2500 block Rondowa Avenue
  • Riverside
  • OH
  • 45404
  • Montgomery
  • 2500 block Rondowa Avenue Riverside OH 45404 Montgomery
  • Riverside Police Department
  • Suicide
  • https://fatalencounters.org/wp-content/uploads/2021/08/Kevlin-Wallace.jpg

Source

Source ID: 30677 - Fatal Encounters

Cross References

This report has possible entries from multiple sources


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 63682. Submitted in Mainchain Tx 0A93212B60EE3BC3B3A25E7A0657743A97B43A26C42C2545A2EADA84636A6FC5, at block height 135725

Transaction details

Tx 0A93212B60EE3BC3B3A25E7A0657743A97B43A26C42C2545A2EADA84636A6FC5
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: NOxCq+loRTecrBlw40zpzOSIXwXxa6NpzmuFS1ETy8diRIrIqZ0UJUGBLJ8XrC1LvoKLja6H1TF0MxKIU5jYaQ==
Raw Tx data:

Hash Comparison

Hash stored in database: d213da01806c45a9432dcc19992b939e0c75c809bd0d19b7a6f65d0de40cb992

Hash from Mainchain Tx: d213da01806c45a9432dcc19992b939e0c75c809bd0d19b7a6f65d0de40cb992

Dynamically generated hash: a5ba323bff3c8fda0771bd19c1b0ff4c04a560ebc1cf6de5244b063a77df5c31

Hashes Match?
NO

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: