Skip to content

enhance explorer ux #416

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
stanlou wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

enhance explorer ux #416

stanlou wants to merge 1 commit into from
+314 −83

Conversation

@stanlou
Copy link
Collaborator

@stanlou stanlou commented Feb 1, 2026

Summary

Changes

  • Search by height only when input is numeric and <= current max height; otherwise treat as hash.
  • Add blocks view under dashboard and link block hashes to block detail page.
  • Update blocks tx table status: use the same success tick as tx detail page, show red “x” for failures, and merge status message into the same column.
  • Make dashboard title and slogan configurable.

@stanlou stanlou self-assigned this Feb 1, 2026
@stanlou stanlou requested a review from rpanic February 1, 2026 16:09
rpanic
rpanic approved these changes Feb 2, 2026
View reviewed changes
packages/explorer/src/components/search/GlobalSearch.tsx
return;
}
useEffect(() => {
const fetchMaxHeight = async () => {
Copy link
Member

@rpanic rpanic Feb 2, 2026

Choose a reason for hiding this comment

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

How often is this updated?

Copy link
Collaborator Author

@stanlou stanlou Feb 2, 2026

Choose a reason for hiding this comment

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

At the moment, it’s updated only on refresh. We could add a polling mechanism here, possibly extending it to other lists like blocks and transactions... ,does that make sense?

packages/indexer/prisma/migrations/20260201142200_transaction_priority/migration.sql
@@ -0,0 +1,10 @@
-- CreateTable
CREATE TABLE "TransactionPriority" (
Copy link
Member

@rpanic rpanic Feb 2, 2026

Choose a reason for hiding this comment

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

Wait - do you have to also have this in the indexer? This is only used by the sequencer's mempool and nowhere else, and the foreign key structure should allow us to omit this in the indexer

Copy link
Collaborator Author

@stanlou stanlou Feb 2, 2026

Choose a reason for hiding this comment

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

it's used by pushUserTransaction which is executed during transaction indexing.

@rpanic rpanic linked an issue Feb 2, 2026 that may be closed by this pull request
Explorer improvements/follow-up #389
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@rpanic rpanic rpanic approved these changes

Assignees

@stanlou stanlou

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Explorer improvements/follow-up

3 participants

@stanlou @rpanic