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
Testnet Example:
The output for block 3226895 is reported with the timestamp 1641849006.
If i convert this back into an actual date like date --date="@1641849006" i get the date Mon, 10 Jan 2022 22:10:06.
DB-Sync/Explorers report Mon, 10 Jan 2022 22:10:25
So there is a 19 seconds offset. And its for all the reported blocks. So either i am converting it wrong, or there is a Bug?
The text was updated successfully, but these errors were encountered:
Event timestamps are inferred from the slot number of the block, but there seems to be some ambiguity on how to translate the interval length between blocks (~20 secs ATM). I found this comment by @KtorZ very insightful:
Testnet Example:
The output for block
3226895
is reported with the timestamp1641849006
.If i convert this back into an actual date like
date --date="@1641849006"
i get the dateMon, 10 Jan 2022 22:10:06
.DB-Sync/Explorers report
Mon, 10 Jan 2022 22:10:25
So there is a 19 seconds offset. And its for all the reported blocks. So either i am converting it wrong, or there is a Bug?
The text was updated successfully, but these errors were encountered: