> ## Documentation Index
> Fetch the complete documentation index at: https://docs.presschain.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Explorer Integration

> Use the Blockscout-based Explorer for chain transparency while preserving PressChain-specific Capsule semantics.

# Explorer integration

The PressChain Explorer repository is based on the Blockscout frontend. That provides a mature foundation for blocks, transactions, addresses, contracts and EVM network inspection.

PressChain-specific product value sits above that generic layer: Capsules, evidence, contributors, provenance, roles and PRESS economic context.

## What Blockscout already solves

A standard Explorer should make it easy to inspect:

* blocks
* transactions
* addresses
* contracts
* transaction input and logs
* token activity where supported
* network health information

There is no reason to recreate those primitives only to give them PressChain colors.

## What PressChain needs to add

A journalism-aware Explorer should understand protocol semantics such as:

* canonical Capsule IDs
* author and outlet context
* content and metadata hashes
* cover media
* revision count
* attached contributors
* official and dispute evidence
* evidence tallies
* role and bond context
* bounty relationships

These are not generic EVM concepts and deserve dedicated views.

## Link semantic records to raw chain data

A Capsule page should provide both a readable record and links to the transaction, contract and events that produced it.

This gives two audiences what they need: readers get a coherent publication history, while developers and auditors can descend into raw chain data.

## Do not fork semantics into Explorer code

Explorer labels should come from the same V3 role, action and model authority used elsewhere. Hard-coding a separate role table inside the frontend invites drift.

The Explorer is a client of the protocol.

## Deep-link pattern

A custom application can link users into Explorer after a transaction:

```ts theme={null}
const explorerTx = `https://explorer.presschain.io/tx/${txHash}`;
```

For custom Capsule routes, use the route shape actually deployed by the Explorer rather than assuming an Ethereum transaction route can represent a Capsule ID directly.

## Verification use case

A newsroom publishes a Capsule and displays a “View verification record” link. The Explorer can show cover media, title, author, content hash and evidence summary, then allow a technical reader to open the originating transaction and contract logs.

That connection between semantic and raw views is what makes an Explorer more than a block browser.

## Upstream boundaries

Blockscout has its own configuration and upgrade process. PressChain docs should point developers toward upstream Blockscout documentation for generic frontend deployment details and focus here on the PressChain-specific configuration and semantic extensions.

That reduces duplicated documentation and makes future Blockscout upgrades easier.