Address
Readable wallet or contract address with truncation, copy-to-clipboard, and optional block-explorer deep link.
For isolated previews, theme switching, and sandbox editing, open the Address playground on holydocs.com .
When to use
Use this component when blockchain context, addresses, chains, token math, or wallet onboarding must stay precise and scannable.
Live Examples
Every example below renders the real component directly inside HolyDocs, followed by the exact MDX you can paste into a page.
Contract Address
Contract docs usually pair an address with its deployment chain.
0x742d...bD68
↗
mdx<Address value="0x742d35Cc6634C0532925a3b844Bc9e7595f2bD68" chain="ethereum" />
Wallet Address
You can also render a wallet address without an explorer target.
0x8ba1...BA72
mdx<Address value="0x8ba1f109551bD432803012645Ac136ddd64DBA72" />
Props
| Prop | Type | Default | Description |
|---|---|---|---|
value | string | -- | Full wallet or contract address to display. |
chain | string | -- | Optional chain key used to build the explorer link. |
Usage
Start from this baseline shape and then tailor the copy, data, or nesting to the page you are writing.
mdx<Address value="0x742d35Cc6634C0532925a3b844Bc9e7595f2bD68" chain="ethereum" />
Tips
- Assume readers are one copy action away from using the value in production. Precision matters more than flair on web3 surfaces.
- Always make the target chain explicit when a component can imply a wallet, explorer, or transaction context.
- Use testnet examples unless the page is explicitly about production contracts or addresses you expect people to reuse.
Related Components
Compact chain indicator for network-specific instructions, examples, and warnings.
More
- Interactive playground: Address on holydocs.com
- Component library index: /components