Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 59,186
| Schulenburg, Texas

Name withheld by police, from Schulenburg, Texas, on 25 March 2021

Victim Info

  • Name withheld by police
  • Unknown
  • Male

Details

A person in a vehicle allegedly fired shots at a deputy from the Harris County Precinct 5 Constable's Office around 3 a.m. Several agencies responded to the pursuit. The chase passed through Houston and Colorado County where authorities said they used spike strips to damage the tires. The driver continued to drive on rims until finally coming to a stop outside of Schulenburg, where he refused to get out. Deputies said the driver continued to flash a handgun and police shut down I-10. Following an hours long standoff, the driver shot and killed himself about 8:50 a.m.

Additional Evidence

  • Name withheld by police
  • Male
  • Race unspecified
  • NA
  • NA
  • I-10
  • Schulenburg
  • TX
  • 78956
  • Fayette
  • I-10 Schulenburg TX 78956 Fayette
  • Harris County Constable's Office Precinct 5, Fayette County Sheriff's Office, Schulenburg Police Department, Flatonia Police Department, Texas Department Of Public Safety
  • Suicide

Source

Source ID: 29892 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 58832. Submitted in Mainchain Tx 476A15DB3BF1EBD9EDD81C811F0763CDA1DEF4FE65810FE1C5267653A97DB7C3, at block height 4908613

Transaction details

Tx 476A15DB3BF1EBD9EDD81C811F0763CDA1DEF4FE65810FE1C5267653A97DB7C3
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: tendermint/PubKeySecp256k1
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: k6VXh+7bpKvHPQqkY2JtiSJq3juiixxah4RZTDJ95rp0aWuTGHNHxapInX15E/WLPIJpSWtR0rVKrI9QKWsw4A==
Raw Tx data:

Hash Comparison

Hash stored in database: 5f28d8161d98119cfea27caad8ce0b088e8e127cd6afa5a802b51f5dc20615a5

Hash from Mainchain Tx: 5f28d8161d98119cfea27caad8ce0b088e8e127cd6afa5a802b51f5dc20615a5

Dynamically generated hash: a37c1f3ad6007962958861090347cc5544c44e891eeb22f0c00de26c4edc3902

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: