Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,469
| Campbell, California

Name withheld by police, from Campbell, California, on 1 August 2020

Victim Info

  • Name withheld by police
  • Unknown
  • Male

Details

8/1/2020: About 7:30 p.m., police received two 911 hang-up calls. Dispatchers called back and a woman answered, but the line was disconnected after dispatchers heard a disturbance. Officers arrived and assisted two children fleeing the residence, and shortly after heard gunshots inside. Officers contacted the woman who originally called, and she told them she had been shot and was unable to escape the home. An armed man came out, but retreated back inside when he saw the officers, following which the officers heard another gunshot. The woman was taken out of the home, and the man was found in the carport with what appeared to be a fatal self-inflicted gunshot. https://www.sfgate.com/news/bayarea/article/Police-Investigating-Shooting-And-Possible-Suicide-15452423.php

Additional Evidence

  • Name withheld by police
  • Male
  • Race unspecified
  • NA
  • NA
  • 870 Old Camden Avenue
  • Campbell
  • CA
  • 95008
  • Santa Clara
  • 870 Old Camden Avenue Campbell CA 95008 Santa Clara
  • Campbell Police Department
  • Gunshot
  • Suicide
  • No
  • 2020

Source

Source ID: 28520 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 68784. Submitted in Mainchain Tx EF35D7EB7081DE1F78EED28456F6766AB7B79A8AF5087EFA5FCD483D008FDDB6, at block height 149229

Transaction details

Tx EF35D7EB7081DE1F78EED28456F6766AB7B79A8AF5087EFA5FCD483D008FDDB6
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: urKsph5JBV0bBwTYQXSUS8ESlpk6IMISIxZbCpiAyhh+r2Fw0kvA9UVFluPnc+eOo7GafAHtAV2cKR74qDiigA==
Raw Tx data:

Hash Comparison

Hash stored in database: 42810b016107e329f2fb138b8826c1a1fb5eb0fbfae9ffe103624b185dd1666e

Hash from Mainchain Tx: 42810b016107e329f2fb138b8826c1a1fb5eb0fbfae9ffe103624b185dd1666e

Dynamically generated hash: 42810b016107e329f2fb138b8826c1a1fb5eb0fbfae9ffe103624b185dd1666e

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: