Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block Time vs Created Time #52

Open
tiger5226 opened this issue Feb 5, 2019 · 2 comments
Open

Block Time vs Created Time #52

tiger5226 opened this issue Feb 5, 2019 · 2 comments

Comments

@tiger5226
Copy link
Contributor

Created time is when we find out about the transaction. Usually this is from when we read it from the mempool. However, with a full resync of chainquery this would be much sooner. In these cases the block explorer should show block time for both fields. If the gap is more than 1 hour a part make them both the blocktime value.

@tzarebczan
Copy link
Contributor

This may be confusing to users (just got me!), we should get it fixed up....

@tzarebczan tzarebczan added the consider soon Discuss this issue at the next planning meeting, then remove this label label Mar 18, 2019
@marcdeb1 marcdeb1 mentioned this issue Apr 6, 2019
@marcdeb1
Copy link
Contributor

marcdeb1 commented Jan 8, 2021

I don't think it makes sense to show Created Time, except if it's a mempool transaction.
Other explorers show a block time as Transaction time, and add a confirmation time :

image

So I would suggest removing Created Time and showing only Block Time, except for mempool transactions, and maybe add a confirmation time with less visibility.

@kauffj kauffj removed the consider soon Discuss this issue at the next planning meeting, then remove this label label Feb 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants