Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Claremont, New Hampshire

Jeffrey Ely, 40, from Claremont, New Hampshire, on 31 March 2021

Victim Info

  • Jeffrey Ely
  • White/European American
  • 40
  • Male

Details

Police responded to a home for a report of gunshots being fired. Jeffrey Ely had barricaded himself inside the home. Gunfire was later exchanged between the Ely and State Police, and police shot and killed Ely.

Additional Evidence

  • Jeffrey Ely
  • 40
  • Male
  • White
  • 247 Sullivan St.
  • Claremont
  • NH
  • 3743
  • Sullivan
  • New Hampshire State Police, Claremont Police Department
  • NH010010X, NH0100600
  • Gunshot
  • Pending investigation
  • No known charges
  • No
  • Allegedly Armed
  • gun
  • attack
  • not fleeing
  • Rural
  • https://fatalencounters.org/wp-content/uploads/2021/04/Jeffrey-Ely.jpg
  • Violent crime
  • gunshots

Source

Source ID: 8729 - 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 65116. Submitted in Mainchain Tx 727BD81174B3F82E79BEDA424D312F67C6DC5A66C83AF874E4055EE4E10447CA, at block height 139450

Transaction details

Tx 727BD81174B3F82E79BEDA424D312F67C6DC5A66C83AF874E4055EE4E10447CA
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: Vb6ja2/KdUwbSe5N4mWraBVpYlc+BSKs5uwkejIk9Yo3soXTmeE5z3zjcO3cBJC8+nc4WSZVBOT8RCmI9vCm6Q==
Raw Tx data:

Hash Comparison

Hash stored in database: 7759e54446ca8e15513e02c63e52446a3d4871eed229b9734db961d6a10b1662

Hash from Mainchain Tx: 7759e54446ca8e15513e02c63e52446a3d4871eed229b9734db961d6a10b1662

Dynamically generated hash: 7759e54446ca8e15513e02c63e52446a3d4871eed229b9734db961d6a10b1662

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: