Transaction history CSV export

[Jaydbrown]

Add an 'Export CSV' action on /transactions.

[temieehade-coder]

@temieehade-coder has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello maintainer, i can fix this issue

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

[Oluwasuyi-Oluwatimilehin-Daniel]

@Oluwasuyi-Oluwatimilehin-Daniel has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello @maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately. And I will deliver at the shortest possible time.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwasuyi-Oluwatimilehin-Daniel to this issue.

[Michael-Olagoke]

@Michael-Olagoke has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer, I've carefully read what the prerequisite for this task should be. I have vast and robust experience in project management as you can confirm from my GitHub profile. I am experienced in all the languages required for this task.

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

[TS-mfon]

@TS-mfon has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

GM

I'm a Blockchain developer

Please can I work on this issue

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

[wenxiaojie1]

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

I will add a tested CSV export path directly from the TransactionRow data already loaded on /transactions: deterministic columns and ordering, RFC 4180 escaping for commas/quotes/newlines, ISO timestamps, full hashes rather than truncated display values, and a safe filename. The action will be unavailable during loading/error/empty states, create and revoke its object URL without leaks, remain keyboard and screen-reader accessible, and be covered by focused serializer and page-interaction tests before typecheck, lint, the unit suite, and build.

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

[dumbdev]

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

Hi Maintainer, I have experience working on this issues
Pls assign it to me

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

[drips-wave]

Congratulations, @dumbdev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @dumbdev: 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 🌊