Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 59,186
| Wauwatosa, Wisconsin

Kevin Wilke, 35, from Wauwatosa, Wisconsin, on 11 March 2021

Victim Info

  • Kevin Wilke
  • Unknown
  • 35
  • Male

Details

Police responded to a retail theft at Best Buy. Before arriving at the store, officers found a car that matched the description of the vehicle believed involved in the theft. They stopped it, one of three occupants fled on foot as officers approached the car. As officers searched for the man, they learned a pedestrian had been struck by a car on I-41 in the area where the suspect was last seen running. The pedestrian who was struck and killed, Kevin Wilke, was believed to have been involved in the retail theft.

Additional Evidence

  • Kevin Wilke
  • 35
  • Male
  • Race unspecified
  • NA
  • NA
  • I-41/US-45 and Burleigh St
  • Wauwatosa
  • WI
  • 53226
  • Milwaukee
  • I-41/US-45 and Burleigh St Wauwatosa WI 53226 Milwaukee
  • Wauwatosa Police Department
  • Pending investigation

Source

Source ID: 29781 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 58769. Submitted in Mainchain Tx FA4CE190FEB501C4B7B82AF737D59652C5BFF8530921369433FDB57E708D0E82, at block height 4819883

Transaction details

Tx FA4CE190FEB501C4B7B82AF737D59652C5BFF8530921369433FDB57E708D0E82
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: tendermint/PubKeySecp256k1
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: I9sz+oTVLLLB7VWckdBL1Zt7JynRfKiGJhRND3oQ3EMxnnZD8JFB+8z4y2ETQb+qOrc1PX3f7f9A7VN4WkxE8Q==
Raw Tx data:

Hash Comparison

Hash stored in database: ae86ee96c1765c29402434aa2dfe6aa7b5260cf3c7ff29214d5b10ea026866f6

Hash from Mainchain Tx: ae86ee96c1765c29402434aa2dfe6aa7b5260cf3c7ff29214d5b10ea026866f6

Dynamically generated hash: 1a3ca45f889c80f1e951c2d78307f4392de5dd45ccb274caa26e8cc34b636e97

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: