ARC MAINNET · READ ONLY

Arc RPC Evidence

Inspect one public receipt or historical header. Keep the observations and their limits together.

One official endpoint · up to 12 sequential attempts · 5 seconds per read · 45-second deadline · 256 KiB per response. No scan, wallet, signature or write method.

Reads go directly from your browser to rpc.mainnet.arc.io. Your public identifiers and IP are visible to that provider. Nothing is saved automatically.

Ready. Block 0 checks genesis when you press Read.

What the verdict means

verified
Returned identifiers and pinned inclusion agree at observation times. This is no independent trust or finality proof.
observed-null
A relevant response was null. Absence, failed execution and pruning are not established.
insufficient-evidence
An error, malformed response, cancellation or budget prevented verification.
inconsistent-observation
Observations disagree. Tip changes or backend lag may cause this; no endpoint misconduct claim.

Execution is reported only after receipt, transaction and pinned-block inclusion agree. Selected header availability does not prove archive-state completeness.