Stellar Expert deep-link helper everywhere

[truthixify]

Tier: S (½-1 day) Type: feature

Context

good-first-issue

Scope

Today some places link to stellar.expert (txs from Send success) and others don't (stealth addresses on Receive, contract events). Add a centralized helper and surface links consistently.

Acceptance criteria

• Centralize URL generation in src/lib/explorer.ts (already exists, extend)
• Helpers: accountUrl, txUrl, contractUrl, assetUrl, operationUrl
• Audit Receive, Send, Activity for missing links
• Add "View on stellar.expert" links wherever a Stellar identifier appears
• Network-aware (testnet vs public)

Files to start with

• Helpers complete
• Audit findings addressed
• Consistent labelling ("View on stellar.expert")
• a11y: rel="noopener"

Why this matters

• src/lib/explorer.ts
• All Stellar components

[uboho-prog]

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

Hello maintainer,

I would like to work on this task.

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

[drips-wave]

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

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

[truthixify]

@uboho-prog Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. If you get stuck or context changes, just say so on the PR — silence is the only thing that costs you the assignment.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building. Looking forward to the PR.