Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,507
| Cleveland , Ohio

Innes Lee Jr., 25, from Cleveland , Ohio, on 15 April 2021

Victim Info

  • Innes Lee Jr.
  • Black/African American
  • 25
  • Male

Details

Around 4 a.m., officers received a call about a man wanted in connection with unspecified crimes. The man "got away," but police returned after receiving a call later in the morning. Officers spotted that person, and after a short foot chase into a backyard, the officer encountered the person, ordered him to put his hands up, to get down. That person allegedly turned on the officer and pulled a gun from his waistband, and the officer shot and killed Innes Lee.

Additional Evidence

  • Innes Lee Jr.
  • 25
  • Male
  • Black
  • 13600 Beachwood Ave.
  • Cleveland
  • OH
  • 44105
  • Cuyahoga
  • Cleveland Police Department
  • OHCLP0000
  • Gunshot
  • Pending investigation
  • No known charges
  • No
  • Allegedly armed
  • gun
  • other
  • foot
  • Urban
  • https://fatalencounters.org/wp-content/uploads/2021/04/Innes-LeeJr.jpg
  • Part 1 Violent Crime
  • warrant (homicide)

Source

Source ID: 9191 - Mapping Police Violence

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 64883. Submitted in Mainchain Tx A6FEB47D7BB3CB44A5C70572DACF4FC707547EF9F3CE296B2E7F3D4D3273A168, at block height 139217

Transaction details

Tx A6FEB47D7BB3CB44A5C70572DACF4FC707547EF9F3CE296B2E7F3D4D3273A168
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: +OnhHk1mmRgl/pkoZR4ccYf7OzPoyOrfPHIad3nr13AERqI1A4cq6/FwS+kNW5PMfbUEU/RApNFgNUsiFalfgQ==
Raw Tx data:

Hash Comparison

Hash stored in database: 25ad3874b103d3eaa6d70d49c5827fc6d9e37f67bd56bed11c9eacc249a71028

Hash from Mainchain Tx: 25ad3874b103d3eaa6d70d49c5827fc6d9e37f67bd56bed11c9eacc249a71028

Dynamically generated hash: dbe5aee786a313bb872fb7689d1440b2779d10b31f8f3f2c9f28c8372529918b

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: