VÖRSANNTruth Cannot Be Hidden.

Evidence & Blockchain

DPAL accountability ledger

DPAL report summaries, server-authoritative PostgreSQL chain registration, browser-local verification and linked Situation Rooms. Persistent DPAL registration is separate from external public-chain anchoring/finality.

About DPAL

Shared report API

CHECKING

Browser chain integrity

checking

Local blocks

0

Latest indexed block

—

Server persistence is confirmed only when the shared API reports PostgreSQL and returns exact block records. Public-chain finality remains separate. Browser verification checks only browser-stored DPAL v1 links.

Multi-state well GIS

Persistent Blockchain Explorer

Search the shared DPAL chain

Search by report ID, block number, block hash, or data hash. Results below come from the PostgreSQL-backed authoritative DPAL v1 chain.

Storage

unconfirmed

Chain ID

—

Latest hash

—

BlockReportBlock hashPreviousPersisted

No persistent blocks matched this search, or the persistent backend is unavailable.

Locations supplied by displayed reports

0 mapped · 0 without usable coordinates. Source coordinates, not surveyed or independently verified positions. Basemap imagery is context, not current methane evidence.

No supplied coordinates. No markers or state-centroid positions have been invented.

Loading shared ledger records…
Blockchain terminology: this page preserves DPAL’s private SHA-256 linked-block ledger. Persistent registration writes canonical report bytes to the PostgreSQL-backed DPAL chain and requires exact readback. Browser-local verification remains separate. External/public-chain finality still requires a canonical network receipt and is not inferred from a string alone.