Tracking issue: Explore for Nerds

[erwanor]

Tracking issue: Inspect Page & Subpages

The Inspect page can also be thought of as “Explore for Nerds”. The goal is that it should be possible to inspect various aspects of the Penumbra DEX structure, the visual display doesn’t matter, but GETTING THE INFORMATION does. Inspect pages are expected to be viewed by only a tiny minority of users. This is distinct from the other pages, which are intended to be used as part of common user flows, and have greater design focus and quality.

Goal: Each “object” relevant to the Penumbra DEX should have its own Inspect subpage with a route /inspect/... that identifies it.

LP View

Route: /inspect/lp/[LPID]

• inspect(lp): LP transaction hashes are incorrect #333

Block

Route: /inspect/block/[HEIGHT]/

• inspect(block): display batch swap information per pair
• inspect(block): display arb information
• inspect(block): display block summary #338

Transaction

Route: /inspect/tx/[HASH]/

• inspect(tx): display transaction from RPC #340
• inspect(tx): fetch transactions from pindexer #350

LP Leaderboard

Route: /inspect/lp-leaderboard

• inspect(ldb): basic leaderboard for positions #359
• inspect(ldb): sort positions by executions, fees, volume
• inspect(ldb): add filters for pair and time range

Landing page

Tagline: “Explore for Nerds”
Route: /inspect/

• inspect: detect input as LP id, TX id, or block height #351
• inspect: display and link to recent non-empty blocks
• inspect: display and link recent transactions

Important: None of these pages should have any queries to the user’s wallet, in other words, we are rendering a “public view” of public data.

[hdevalence]

I think we should drop / defer the position leaderboard part, since it should be done as part of LQT work.

We need a way to link to a specific SwapExecution, so that we can cross reference:

• when showing a trade in the trade list, can click through to inspect view for that swap execution
• when showing a position execution in the LP inspect view, can click through to see the context an execution happened in

I think this + tx info (being able to link to transactions) is a good first step for showing the discovery cycles of DEX activity.