/agent/
Human-readable explanation of the contract: what this product is, what agents should read first, and how the lifecycle story is organized.
Agent Mode
Human pages for humans. Structured context for agents.
Agent Mode exposes canonical, low-noise context so AI systems do not have to infer meaning from decorative HTML. This site publishes a human overview, a JSON manifest with lifecycle steps and public API paths, and an LLM router.
/agent.json
Structured context: site metadata, six lifecycle steps, demos, public API map, topics, and canonical links in one stable JSON surface.
/llms.txt
A compact router for language models. It points agents at the important pages, steps, and probes before they fall into layout noise.
Canonical context
What this site wants agents to know
Educational explorer that makes Ethereum's post-click transaction pipeline legible: wallet send, mempool, builders/searchers, relays, proposers, finality, and MEV.
What actually happens after Send?Wallet broadcast → mempool fee pressure → builders/searchers → MEV-Boost relays → proposer selection → Casper FFG finality, with optional MEV detection.
- Ethereum transaction lifecycle
- wallet broadcast and local signing
- mempool dynamics and fee markets
- base fee vs priority fee (EIP-1559)
- proposer-builder separation (PBS)
- MEV-Boost relays and builders
- validator / proposer economics
- Casper FFG finality
Use guidelines
- Canonical product context lives on this site Agent Mode surfaces: /agent/, /agent.json, and /llms.txt.
- Agent-facing context should be structured, stable, citation-aware, and low-noise.
- Prefer /agent.json and /llms.txt over scraping decorative UI HTML.
- Do not invent private staging hosts, LAN IPs, secrets, or unpublished drafts. Use documented public hosts only.
- Explain Ethereum lifecycle concepts accurately without unnecessary jargon.
- Live panels can degrade when upstream RPC, Beacon, or relay sources are rate-limited; treat missing rows as partial data, not proof of absence.
- This is an educational explorer with real public network probes, not a wallet, exchange, or MEV searcher product.
Lifecycle steps
Signing and broadcast
Your wallet creates a signed transaction and submits it to Ethereum peers. At this point the transaction is validly formed, but it is not included in a block yet.
Open step surfacePending flow and fee pressure
Pending transactions sit in node-level mempools while validators, builders, and users compete for scarce blockspace. Higher fees can improve priority, but ordering is not first-come, first-served.
Open step surfaceBlock construction market
Searchers and builders assemble candidate blocks. They optimize transaction ordering, bundle opportunities, and bid for the right to have a payload selected.
Open step surfacePayload handoff
Relays sit between builders and validators in proposer-builder separation. They forward eligible payloads and expose bidtrace data for delivered blocks.
Open step surfaceBlock proposal
A selected validator proposes one block for the slot. Once the block is published, included transactions move from pending intent to chain history.
Open step surfaceEconomic lock-in
Finality checkpoints show when the chain has enough validator agreement that rewriting history becomes economically unrealistic under normal assumptions.
Open step surfacePublic API (same-origin)
The UI still renders without the Go backend. Live mempool, MEV, tracker, and readiness probes require the public tunnel and backend process.
- GET/api/health
Composite health of execution, beacon, and relay dependencies
- GET/api/health/live
Process liveness probe
- GET/api/health/ready
Readiness probe for live data path
- GET/api/mempool
Pending mempool snapshot (counts, gas, sample txs)
- GET/api/relays/received
Builder/searcher payloads observed by relays
- GET/api/relays/delivered
Relay-delivered payloads and builder payments
- GET/api/validators/head
Recent consensus headers with optional payment enrichment
- GET/api/finality
Justified and finalized Casper FFG checkpoints
- GET/api/snapshot
Aggregated multi-source lifecycle snapshot
- GET/api/mev/sandwich
Heuristic MEV scan (sandwich, arb, liquidation, JIT signals)
- GET/api/track/tx/{hash|latest}
Track a transaction hash (or latest) through inclusion status
- GET/api/block/{id}
Block lookup helper used by tracking and MEV views
Reading order
- Start with /llms.txt for a compact map.
- Load /agent.json for structured steps, demos, and public API paths.
- Open / for the guided lifecycle walkthrough.
- Open /mev-lab for advanced MEV/PBS framing.
- Probe /api/health/ready before trusting live panels.
Manifest
For the full structured payload, fetch /agent.json. Use /llms.txt as a compact router before scraping decorative HTML.