Skip to content
This repository has been archived by the owner on May 24, 2022. It is now read-only.

Transaction confirmation status is incorrect #324

Closed
ltfschoen opened this issue Dec 25, 2018 · 0 comments
Closed

Transaction confirmation status is incorrect #324

ltfschoen opened this issue Dec 25, 2018 · 0 comments

Comments

@ltfschoen
Copy link
Contributor

When I submit a valid transaction to send Ether or THIBCoin, it stays on the "Submitted" screen as shown below saying that it's "Waiting for block confirmations"
screen shot 2018-12-26 at 7 54 57 am

However when I viewed the transaction and kept refreshing it in Blockscout or Etherscan it would show that numerous confirmations had occurred. Even right up to the last block confirmation (i.e. 139) it still showed "Waiting for block confirmations" in the UI.

And in the Electron bash terminal it showed that I was synchronised to the latest block and had 17/50 peers.

Once all the block confirmations had completely it did successfully display "Transaction confirmed" as shown below:

screen shot 2018-12-26 at 8 24 29 am

Note that I am tethering on an 8Mbps download and 1Mbps upload connection.

Previously when I've used Fether it would show the block confirmation progress in the UI, but now it just says that it's "Waiting for block confirmations" even right up to the last block confirmation, so as a user whilst I think it may not have frozen since it's showing the blue dots animating on the "Submitted" screen, I actually have no idea how much it's progressed (if at all) and how long I may need to wait.

So I think we should add a link to BlockScout on the "Submitted" screen so the user can check the block confirmation progress (i.e. "See it on BlockScout") just like we already have on the "Transaction confirmed" screen #314. Also we need to investigate why it isn't displaying the block confirmation progress in the Fether UI as it used to.

@Tbaut Tbaut modified the milestones: 0.4, 0.5, 0.6 ... Jan 3, 2019
amaury1093 added a commit that referenced this issue Jan 21, 2019
fix: Relates to #324. Show link to Blockscout upon confirmed, not the first confirmation
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants