Stellar block explorer integration recipe

[truthixify]

Labels: Stellar Wave, stellar, docs, drips, help-wanted, good-first-issue
Tier: S (½–1 day)
Type: writing

Context

Integrators frequently want to link from their UI to a Stellar block explorer (stellar.expert, StellarChain, or the Soroban-focused explorers). The patterns are non-obvious — testnet vs. mainnet URL bases, how to deep-link to a contract vs. account vs. tx, how to render a stealth address (which is a normal Stellar account, but the conceptual context matters).

Scope

Write docs/guides/stellar-explorer-recipes.mdx covering:

1. URL patterns for stellar.expert (the recommended explorer):
   • Account: https://stellar.expert/explorer/{testnet|public}/account/{G...}
   • Transaction: https://stellar.expert/explorer/{testnet|public}/tx/{hash}
   • Contract: https://stellar.expert/explorer/{testnet|public}/contract/{C...}
   • Asset: https://stellar.expert/explorer/{testnet|public}/asset/{code}-{issuer}
2. A small TypeScript helper stellarExplorerUrl(kind, value, network) that integrators can copy.
3. UX guidance: when to show explorer links (always after a successful tx), how to label them ("View on stellar.expert" not "Open in explorer"), and a11y considerations (rel="noopener").
4. Alternative explorers — brief mention of stellarchain.io and StellarBeat with their URL patterns for completeness.
5. A Stellar-stealth-address-specific section: "What does it mean to view a stealth account on the explorer?" — the explorer shows the account's full history; the privacy guarantee is that the account is unlinkable to your identity, not that the account is private from the explorer.

Acceptance criteria

• Page committed and linked from the SDK Stellar page and the Stellar quickstart.
• Helper function included as a runnable snippet.
• Privacy clarification section is explicit — readers should never confuse "explorer transparency" with "privacy break."

Why good-first-issue

Self-contained, no original engineering, but writing well requires care. Good showcase for a contributor's docs voice.