You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When making a transaction if the transaction for some reason is not confirmed or does not reach mempool, the user can see that transaction in the app interface for the next 100 blocks (approximately 2 and 1/2 hours), this is a lot of waiting time.
My understanding is that the standard is 40-45 blocks, although for me it would be fine to wait much less, I consider that at least the standard should be the one used and so the wait is less.
Although the image may be a bit alarming (it is related to another error), I just want to show how long the transactions have remained on the screen.
It is 18:42 hours and the first transactions were made at 17:15 hours, while the others already have 42 minutes on screen, in the same way it happens with any transaction that is not confirmed.
The text was updated successfully, but these errors were encountered:
When making a transaction if the transaction for some reason is not confirmed or does not reach mempool, the user can see that transaction in the app interface for the next 100 blocks (approximately 2 and 1/2 hours), this is a lot of waiting time.
My understanding is that the standard is 40-45 blocks, although for me it would be fine to wait much less, I consider that at least the standard should be the one used and so the wait is less.
Although the image may be a bit alarming (it is related to another error), I just want to show how long the transactions have remained on the screen.
It is 18:42 hours and the first transactions were made at 17:15 hours, while the others already have 42 minutes on screen, in the same way it happens with any transaction that is not confirmed.
The text was updated successfully, but these errors were encountered: