lbryio / lbryio/block-explorer

transactions for a block should be listed in the order that they exist in the block

Open
#63 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
17
Forks
24
PR merge metrics
No merged PRs in 30d

Description

```
"d33b00cb796d3fd510470a2dff741a5534c457d6e9468fc57dd122cbaeb2351c",
"02c8ede0b6c950a2067ab31fbfe162bf9614712fe673bd15ad4e55bbe54afbbb",
"98e93843c1d442e276761b387c260d0e620011b823f32b65eb28073c7a1fccf7",
"b8d2725b2f8e65de95a78114e6ac1dc728208a5989d1e5d65761197798bc2ca2"

```
vs
![image (1)](https://user-images.githubusercontent.com/1509322/58593343-e0e5c200-8227-11e9-80f6-9d0dc6031e52.png)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the discrepancy shown in the issue and compare the displayed transaction hashes with their order in the block. Trace the block-explorer path that fetches and renders a block's transactions; done means the listed order matches the order stored in the block.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
blockchain
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.