dusk-network / dusk-network/explorer
explorer: Add Address and Transaction Information
Open
Nobody has claimed this yet.
need:breakdown
need:feedback
need:specs
type:feature
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description
It has been suggested that the Explorer should contain detailed information about addresses and their associated transactions. With the introduction of Moonlight (which is fully public), this functionality should now be possible.
Expected Functionality
- The Explorer should provide information about addresses and their transactions, similar to the way it is done on Etherscan (e.g., example link).
- Apart from transactions, Etherscan also provides:
- Token Transfers
- Produced Blocks
- Analysis of the account
- Additionally, it includes a page that lists the top accounts by ETH balance (example link).
Considerations
- Review what information is relevant and useful for our users and determine which features make sense to implement for the Dusk Explorer.
- Create appropriate designs for the updated Explorer views.
- Ensure there is an API (e.g., w3sper SDK) available to retrieve the necessary data for the new features.
Tasks
- Research which Etherscan features are relevant for our Explorer.
- Confirm data retrieval is possible through an appropriate API (such as the w3sper SDK).
- Design and propose the layout for these features in our Explorer.
- Implement and test the new Explorer functionality.
References
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the Etherscan address and accounts examples, then investigate whether the w3sper SDK can provide the required data. Define the relevant feature scope and Explorer layouts before implementing and testing the functionality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, blockchain, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100