Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 59,186
| Minneola, Kansas

James "Jim" Crosby Wright, 67, from Minneola, Kansas, on 9 March 2021

Victim Info

  • James "Jim" Crosby Wright
  • White/European American
  • 67
  • Male


Around 7 p.m., Jim Wright's family member reported to the Meade County Sheriff's Office that they were concerned about his welfare. Deputies found him near the Clark County and Meade County line. Wright fled in his SUV, and deputies pursued. Deputies deployed spike strips, and Wright's SUV slowed and came to a stop. Wright got out of his vehicle holding a firearm. Deputies and officers gave commands for him to drop the gun. Around 9:40 p.m., officers from various agencies shot and killed him.

Additional Evidence

  • James "Jim" Crosby Wright
  • 67
  • Male
  • European-American/White
  • European-American/White
  • Not imputed
  • US-283 and Ash St.
  • Minneola
  • KS
  • 67865
  • Clark
  • US-283 and Ash St. Minneola KS 67865 Clark
  • Meade County Sheriff's Office, Clark County Sheriff's Office, Ford County Sheriff's Office, Kansas Department of Wildlife, Parks and Tourism
  • Pending investigation


Source ID: 29772 - Fatal Encounters


Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 58782. Submitted in Mainchain Tx 7246F06EBE9F01504F8589FD430595EBD1F07E54B72477767327EA4CB8507707, at block height 4819961

Transaction details

Tx 7246F06EBE9F01504F8589FD430595EBD1F07E54B72477767327EA4CB8507707
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: tendermint/PubKeySecp256k1
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: KM8hoOm4+DIMuWmyhu4CGDqw7H1PVtqx03Pm7z3kXNlJIkYYneRMRCybkCXyrjMMQbyzG1dPqgaU5zj6ocXHVA==
Raw Tx data:

Hash Comparison

Hash stored in database: 41af181d7a3b6e66844c9c22187c37cbd80241c96282941c78e2c77654587fa6

Hash from Mainchain Tx: 41af181d7a3b6e66844c9c22187c37cbd80241c96282941c78e2c77654587fa6

Dynamically generated hash: b981d4332fed4ff67a44034d0bc1fdf8b1e7e38c3259c66f796147b55eed89bf

Hashes Match?

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: