Add helper for converting a ledger sequence number to an estimated timestamp

[Chucks1093]

Summary

Several parts of the UI display event timestamps that come from the server as ledger sequence numbers. Converting a ledger sequence to an approximate UTC timestamp (using Stellar's ~5 second ledger time) should be a shared helper rather than being calculated inline in components.

Scope

• Add ledgerToTimestamp(ledger: number, referenceLedger: number, referenceTimestamp: number): Date helper
• Calculation: referenceTimestamp + (ledger - referenceLedger) * 5000 (5 seconds per ledger in ms)
• Add unit tests for: ledger in the past, ledger in the future, ledger equal to reference

Acceptance Criteria

• Helper returns correct estimated Date for past and future ledgers
• Ledger equal to reference returns exactly the reference timestamp
• Unit tests cover all three cases

ETA: 12 hours

---

Coordinate on Telegram

[MoscowDev]

I’d love to take this issue on. I’ve worked on production-ready applications and collaborated extensively through GitHub workflows. I’ll dig into the current setup, implement a solid and reliable fix, and deliver a well-tested PR. My focus is on clean, maintainable code and fast, dependable delivery.

[MoscowDev]

I’d love to take this issue on. I’ve worked on production-ready applications and collaborated extensively through GitHub workflows. I’ll dig into the current setup, implement a solid and reliable fix, and deliver a well-tested PR. My focus is on clean, maintainable code and fast, dependable delivery.

[midexol]

Hi maintainer, can I get to work on this?

[forexlord]

@forexlord has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, i would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @forexlord to this issue.

[kodinaka30-ship-it]

@kodinaka30-ship-it has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I'd like to work on this because scattered inline timestamp math across components is exactly the kind of small inconsistency that leads to bugs later, and consolidating it into one shared helper makes the codebase easier to trust and maintain. I'm comfortable implementing ledgerToTimestamp with the straightforward referenceTimestamp + (ledger - referenceLedger) * 5000 calculation and making sure it handles both past and future ledgers correctly. I'll add unit tests covering a past ledger, a future ledger, and the ledger-equal-to-reference case to confirm the helper behaves exactly as specified.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @kodinaka30-ship-it to this issue.

[Henrichy]

@Henrichy has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Good day Maintainer
I’m a smart contract and full-stack developer who turns complex ideas into secure, production-ready blockchain code. With strong skills in Rust and Solidity, I build systems that are fast, safe, and built to last.
My experience with the Stellar SDK and Soroban lets me ship real-world Web3 solutions that actually move value.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Henrichy to this issue.

[iwayemi5]

@iwayemi5 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to work on this issue as I have reviewed the scope I think I should have a PR ready in 50 minutes.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @iwayemi5 to this issue.

[covenantalade]

@covenantalade has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Let me work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @covenantalade to this issue.

[grantfox-oss]

🦊 GrantFox — @covenantalade has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #446)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @covenantalade! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @covenantalade: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@covenantalade's PR #451 was approved and merged by @Chucks1093.

🏆 @covenantalade: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (83 total points). Track your full progress on GrantFox.

👏 Great work, @covenantalade! Keep contributing to accesslayerorg.