Skip to content

feat(internal-explorer): local txn links, inclusion latency, and zeronet active blocks - #104

Open
niran wants to merge 3 commits into
mainfrom
fix/tips-block-tx-links
Open

feat(internal-explorer): local txn links, inclusion latency, and zeronet active blocks#104
niran wants to merge 3 commits into
mainfrom
fix/tips-block-tx-links

Conversation

@niran

@niran niran commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Block transaction rows always open the local transaction page, including bundled and metered txs that previously wrapped to the bundle page or only linked out to Blockscout.
  • Transaction On-chain status links to Basescan and Blockscout when the chain has them (Zeronet has neither).
  • When inclusion events exist, the block list shows latency from the first observed event to inclusion. BUILDER_FLASHBLOCK_PUBLISHED counts as inclusion; later block-inclusion events are ignored when that flashblock confirmation exists.
  • Zeronet can jump to the latest block with user transactions, and every zeronet block page can walk back to the previous active block. System sender is the L1 attributes deposit address.

Test plan

  • Open an Internal Explorer block with user transactions and confirm every row goes to /internal-explorer/txn/<hash>, not Blockscout and not the bundle page.
  • On that txn page, confirm View on Basescan and View on Blockscout sit in On-chain status on mainnet/sepolia, and that Zeronet omits them.
  • On a chain with audit configured, confirm the Latency column appears only when at least one tx has inclusion events, and that a flashblock publish is preferred over a later BUILDER_INCLUDED.
  • Confirm bundled txs still show the execution heatmap on the block page.
  • On zeronet, use Latest active block from the dashboard and Previous active block from a quiet head block; both should land on a block with user transactions.

type=routine
risk=low
impact=sev5

…tency

Block rows always go to the local transaction page, and txn On-chain
status links out to Basescan and Blockscout. When inclusion events
exist, each row also shows total latency from first observed event.
@cb-heimdall

Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

@vercel

vercel Bot commented Aug 27, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
omni-ui Ready Ready Preview Aug 27, 2026 4:24am

Request Review

…locks

Zeronet heads are often L1-attributes-only. The block list can jump to
the latest block with user transactions, and every zeronet block page
can walk back to the previous one.
@niran niran changed the title feat(internal-explorer): link block txs locally and show inclusion latency feat(internal-explorer): local txn links, inclusion latency, and zeronet active blocks Aug 27, 2026
@niran
niran requested a review from montycheese August 27, 2026 04:08
Stop the block-row latency span at the first BUILDER_FLASHBLOCK_PUBLISHED
instead of waiting for a later block-inclusion event.
Comment thread .env.example
# Per-chain block explorer for Internal Explorer links (client-visible). Defaults:
# Per-chain Blockscout URL for Internal Explorer links (client-visible). Defaults:
# mainnet=https://base.blockscout.com, sepolia=https://base-sepolia.blockscout.com.
# Transaction pages also link to Basescan on mainnet and sepolia. Zeronet has

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you mean blockscout here, right?

Comment thread next.config.mjs
// is not mistaken for a nested package of the parent lockfile.
outputFileTracingRoot: dir,
turbopack: {
root: dir,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did something change that required this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants