Gregory Putnik, 32, from Fresno, California, on 18 October 2020
Victim Info
- Gregory Putnik
- White/European American
- 32
- Male
Details
Officers first responded to a failed carjacking by Putnik. Putnik had ran to a nearby home and climbed onto the roof. The homeowner came outside of their home with a rifle, confronted Putnik, and scared him off the property. Outside, Putnik was confronted by another neighbor and the two engaged in a physical altercation. Officers arrived on the scene, and Putnik ran into the same home he had climbed up onto. Inside the home, Putnik secured the homeowner's rifle and allegedly fired at a group of teenagers and officers. Officers fired bean-bag rounds at Putnik, and later shot him.Primary Evidence & Links
Additional Evidence
- Gregory Putnik
- 32
- Male
- White
- N Weber Ave & W Olive Ave
- Fresno
- CA
- 93728
- Fresno
- Fresno Police Department
- Gunshot
- Pending investigation
- No known charges
- No
- gun
- attack
- Foot
- No
- 6245
- Urban
- https://fatalencounters.org/wp-content/uploads/2020/11/Greg-Putnik-JPG.jpg
Source
Source ID: 8525 - Mapping Police Violence
Cross References
This report has possible entries from multiple sources
- Washington Post -Gregory Putnik, 32, from Fresno, California - shot on 18 October 2020
- Killed By Police -Gregory Putnik, 32, from California on 18 October 2020
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 67348. Submitted in Mainchain Tx 505C8313FAB1A4C3717C0EFEF7B014B0B8B345E696D193EF304022152B4028FF, at block height 145502
Transaction details
Tx 505C8313FAB1A4C3717C0EFEF7B014B0B8B345E696D193EF304022152B4028FF
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: DIYpIZhhzm67BXaGcWFq2OyiT31+y3pXWry9mHGjqVEMxmja+NA24SDO9UNGdWVS/cenmgcauvTPTZTSElZSyw==
Raw Tx data:
Hash Comparison
Hash stored in database: 049e33b3476c11649d832c2b1231fc3a101fbd863f0e3e55e6fe7d1363346a0c
Hash from Mainchain Tx: 049e33b3476c11649d832c2b1231fc3a101fbd863f0e3e55e6fe7d1363346a0c
Dynamically generated hash: 21ad69a80211b2029fb581eca19cd333d0c7afa657494ab7d29c52ae883ee758
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: