Conversation
explorer: Improve SearchNotification appearance
Resolves #1887
explorer: implement loader
explorer: Add service method to check for stale market data
explorer: Avoid restart market data polling in case of 429 error
Resolves #1933
explorer: Give defaults to data fetch intervals
Resolves #1937
Resolves #1938
explorer: Remove market poll restart after an error
explorer: update DataCard design
- Updated vite build target to support top-level await Resolves #1946
explorer: Save market data in local storage
explorer: Delay fetching market data if the current data is not stale
Resolves #1960
explorer: fix retry on chain info tables
Resolves #1972
explorer: Upgrade to Vitest 2.x
Resolves #1976
Resolves #3699
explorer: Add value property to Transaction Details
explorer: Change transaction list to use a single GraphQL query
Resolves #3741
explorer: Release v1.4.0
Resolves #3753
Resolves #3757
Resolves #3760
- The `from` and `to` fields are now always shown in moonlight transactions regardless of the transaction's type Resolves #3804
…lorer explorer: Fetch supply from supply.dusk.network, simplify market data fetching
- Add column sorting to the active provisioner list - Add display of owner/consensus key separation for stakers - Introduce rank column based on stake amount
explorer: Replace last100BlockTxs with total transaction stats
- Remove cursor pointer - Hide provisioners without active or locked stake - Fix provisioner ranking based on full list - Refactor key separation & ownership logic - Enriched ProvisionerCard props and fixtures
- added `.nvmrc` file Resolves #3985
Resolves #3987
explorer: replace badly written `makeNodeUrl` test
Resolves #4002
ascartabelli
approved these changes
Feb 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Move the current Explorer app + its monorepo-era git history (previously
dusk-network/rusk/explorer/) back intodusk-network/explorer, while preserving the existing standalone repo history.What’s Included
explorer-*tags.--allow-unrelated-historiesmerge.package.json, changelog/release links).svelte-kit syncruns before lint; increase one test timeout).How To Test
source ~/.nvm/nvm.sh && nvm usenpm cinpm run checksnpm run buildFollow-ups
After
ruskremovesexplorer/, we transfermodule:explorerissues fromdusk-network/rusktodusk-network/explorer.Furthermore, we need to update app deployments to align with the new repo.