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

Unstable timestamp for pending transactions #1118

Open
komret opened this issue Jul 31, 2024 · 1 comment
Open

Unstable timestamp for pending transactions #1118

komret opened this issue Jul 31, 2024 · 1 comment

Comments

@komret
Copy link

komret commented Jul 31, 2024

I noticed this when implementing trezor/trezor-suite#12975.

Pending transactions have a timestamp (first seen), but this timestamp keeps changing over time. See these screenshots of the same transaction in block explorer taken today:

Morning:
Screenshot 2024-07-31 at 10 00 13

Afternoon:
Screenshot 2024-07-31 at 18 19 15

In fact, this transaction was broadcast sometime in May.

@martinboehm
Copy link
Contributor

Unfortunately, as of now, Blockbook is not storing mempool transactions between restarts. Therefore, the first seen time is reset by restart of the service (this is not very frequent but happens from time to time due to maintenance reasons).

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

2 participants