Add `SenderDashboard` with stream creation history and analytics

[ritik4ever]

Problem

SenderDashboard.tsx exists but may be a stub. Senders have no dedicated analytics view showing their total streamed amount, active streams, and history.

Scope

Build out SenderDashboard with aggregate stats fetched from /api/stats and /api/streams?sender=<address>.

Acceptance criteria

• Cards: total streams created, total amount streamed, active streams, completed streams
• Bar chart: streams by status
• Recent activity feed: last 10 events from /api/events?sender=<address>
• Quick action buttons: Create Stream, Bulk Cancel
• Vitest test renders with mocked API data

Complexity: Medium · 150 points

[espcris05-commits]

/attempt #392

I'd like to add SenderDashboard with stream creation history and analytics.

Wallet USDC: GCR377MUJ75YKFLNZKT6XPWNDUIEDZDUHUWY5E2LHOBBSSJDU7MJRZXF
Wallet BNB: 0x6851F2cCD4C4EA991734FAA83c027A909f2703f3

[N-thnI]

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

Dear maintainer
Please assign me this issue

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

[superstarflayce]

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

I’ll love you work on this project

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

[LawalRahman]

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

Hi,

I’m a full-stack and blockchain developer with experience building fintech and payment-focused applications. I work across frontend, backend, APIs, and smart contract integrations with a strong focus on turning ideas into working products quickly.

For this issue, I’d focus on delivering a simple but well-structured solution that demonstrates clear Stellar utility rather than unnecessary complexity. My priority would be reliability, clean architecture, secure implementation, and an MVP that can realistically evolve beyond the hackathon.

I’m ready to begin immediately and ship iteratively with clear progress updates.

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

[drips-wave]

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

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