dusk-network / dusk-network/explorer
explorer: Transaction Details Enhancement
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description
Currently, under transaction details, from and to fields are displayed (inferred from the transaction payload) – these are linking to the account overview page with the specific to or from address. This is currently applied only for Moonlight transfer transactions.
The improvement involves:
- Displaying
fromandtofields independently. Iffromis available buttois not, onlyfromshould be displayed. - Supporting contract operations with addresses in formats such as
0200000000000000000000000000000000000000000000000000000000000000. - Future-proofing for eventual token address pages for this type of address.
Acceptance Criteria
fromandtofields are displayed independently based on availability.- Contract operations with address formats like
0200000000000000000000000000000000000000000000000000000000000000are displayed properly (ie. not as links for the time-being).
Additional Context
These changes will enhance the flexibility and robustness of the transaction details display, especially for contract operations and partial payloads.
Implementation Details
- Update transaction detail rendering logic to handle
fromandtofields independently. - Add support for recognizing contract operation addresses.
Tagging @Neotamandua to review, as the issue was initially raised by him.
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
Start by locating the transaction detail rendering logic and the address-handling code in the explorer. Check how Moonlight transfer from and to values are currently linked, then verify independently available fields and contract-operation addresses against the stated acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100