Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Dayton, Ohio

Benjamin Price Cotton, 24, from Dayton, Ohio, on 12 March 2021

Victim Info

  • Benjamin Price Cotton
  • White/European American
  • 24
  • Male

Details

Following multiple encounters with police over two days, Benjamin Cotton was shot and killed when he allegedly approached officers with a knife, after having stabbed his father. Cotton was described as high on methamphetamine.

Additional Evidence

  • Benjamin Price Cotton
  • 24
  • Male
  • White
  • 2275 Sherer Avenue
  • Dayton
  • OH
  • 45414
  • Montgomery
  • Dayton Police Department, Montgomery County Sheriff's Office
  • OH0570200, OH0570000
  • Gunshot, Taser
  • Pending investigation
  • No known charges
  • Drug or alcohol use
  • Allegedly Armed
  • knife
  • other
  • Not fleeing
  • no
  • 6703
  • Suburban
  • https://fatalencounters.org/wp-content/uploads/2021/03/Benjamin-Price-Cotton.jpg
  • Violent Crime
  • stabbing

Source

Source ID: 8792 - 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 65376. Submitted in Mainchain Tx B9544FB8D04D4F5AE3C3C1BC7398B01EA8B134FD000C0D18887C5AA400717320, at block height 140475

Transaction details

Tx B9544FB8D04D4F5AE3C3C1BC7398B01EA8B134FD000C0D18887C5AA400717320
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: 4FUq2yJSfNCCtB8PZ5wv2h+vKVsYzVmqkv6agdhFZO8gZmD0CYMyNNSfJRrPBuFLaXLdUQ38dK+ca5vsZJh1+A==
Raw Tx data:

Hash Comparison

Hash stored in database: 7d0f56c9084e2ec5f755ac4cc20eeb8f8c242b1c6665ffefd5f23a3630a0e9b3

Hash from Mainchain Tx: 7d0f56c9084e2ec5f755ac4cc20eeb8f8c242b1c6665ffefd5f23a3630a0e9b3

Dynamically generated hash: 7d0f56c9084e2ec5f755ac4cc20eeb8f8c242b1c6665ffefd5f23a3630a0e9b3

Hashes Match?
YES

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: