TxHash
Transaction hash chip with truncation, copy action, and explorer link for deployment guides or transaction walkthroughs.
For isolated previews, theme switching, and sandbox editing, open the TxHash 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.
Ethereum Transaction
Link a deployment or governance action straight to the explorer.
0xabc1...1234
↗
mdx<TxHash hash="0xabc123def456789012345678901234567890abcdef123456789012345678901234" chain="ethereum" />
Base Transaction
Works the same way across supported chains.
0xdef9...0fed
↗
mdx<TxHash hash="0xdef9876543210fedcba9876543210fedcba9876543210fedcba9876543210fed" chain="base" />
Props
| Prop | Type | Default | Description |
|---|---|---|---|
hash | string | -- | Full transaction hash to show and copy. |
chain | string | -- | Optional chain key used to build the explorer URL. |
Usage
Start from this baseline shape and then tailor the copy, data, or nesting to the page you are writing.
mdx<TxHash hash="0xabc123def456789012345678901234567890abcdef123456789012345678901234" 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
Readable wallet or contract address with truncation, copy-to-clipboard, and optional block-explorer deep link.
More
- Interactive playground: TxHash on holydocs.com
- Component library index: /components