incorrect incoming tx / amount #3

Closed
opened 2017-10-11 02:44:52 +02:00 by tzarebczan · 1 comment
tzarebczan commented 2017-10-11 02:44:52 +02:00 (Migrated from github.com)

Sent you this one a while ago: https://explorer.lbry.io/address/bXikZS1g1jvjV1vSB83nPkaEXGZTKoms4f

Looks like it should only have 1 input from: https://explorer.lbry.io/tx/8694118779e15f97bbc79803a67e1f67528f1f6d0aaa5172bb473774aaa72328?address=bXikZS1g1jvjV1vSB83nPkaEXGZTKoms4f#bXikZS1g1jvjV1vSB83nPkaEXGZTKoms4f because the other one links to this tx: https://explorer.lbry.io/tx/0cb62edff9a3ec4478f0a8b8b57b227142cee626c559f5352a54fb333fec17ca?address=bXikZS1g1jvjV1vSB83nPkaEXGZTKoms4f#bXikZS1g1jvjV1vSB83nPkaEXGZTKoms4f which shows 0 coming from that address.

Internal Use

Acceptance Criteria

Definition of Done

  • Tested against acceptance criteria
  • Tested against the assumptions of the user story
  • The project builds without errors
  • Unit tests are written and passing
  • Tests on devices/browsers listed in the issue have passed
  • QA performed & issues resolved
  • Refactoring completed
  • Any configuration or build changes documented
  • Documentation updated
  • Peer Code Review performed
Sent you this one a while ago: https://explorer.lbry.io/address/bXikZS1g1jvjV1vSB83nPkaEXGZTKoms4f Looks like it should only have 1 input from: https://explorer.lbry.io/tx/8694118779e15f97bbc79803a67e1f67528f1f6d0aaa5172bb473774aaa72328?address=bXikZS1g1jvjV1vSB83nPkaEXGZTKoms4f#bXikZS1g1jvjV1vSB83nPkaEXGZTKoms4f because the other one links to this tx: https://explorer.lbry.io/tx/0cb62edff9a3ec4478f0a8b8b57b227142cee626c559f5352a54fb333fec17ca?address=bXikZS1g1jvjV1vSB83nPkaEXGZTKoms4f#bXikZS1g1jvjV1vSB83nPkaEXGZTKoms4f which shows 0 coming from that address. ## Internal Use ### Acceptance Criteria 1. 2. 3. ### Definition of Done - [ ] Tested against acceptance criteria - [ ] Tested against the assumptions of the user story - [ ] The project builds without errors - [ ] Unit tests are written and passing - [ ] Tests on devices/browsers listed in the issue have passed - [ ] QA performed & issues resolved - [ ] Refactoring completed - [ ] Any configuration or build changes documented - [ ] Documentation updated - [ ] Peer Code Review performed
tiger5226 commented 2019-03-19 03:20:08 +01:00 (Migrated from github.com)

Solved with Chainquery integration

Solved with Chainquery integration
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
LBRYCommunity/block-explorer#3
No description provided.