Tools
Local, read-only tools that model Atomicals behavior without ever signing, broadcasting, or sending your data anywhere.
Editorial Verified 2026-08-31
Navigation or explanatory writing with no source-sensitive claim of its own.
- Page ID
-
tools/index - Normative authority
- No normative source. Navigation only.
- Networks
- mainnet
- Documentation version
- 2026.08
- Audience
- everyone, developer
- Owner
- bitcoin-universe-docs
本頁內容尚未翻譯。
- Before you move anythingAllocation visualizer
Model inputs and outputs and see exactly which units land where, and which burn.
- Before you signTransaction inspector
Parse a transaction or PSBT locally and read its inputs, outputs, and signature scope.
- Before you grindBitwork estimator
Model a prefix and see the search space, with honest uncertainty.
- Before you runCLI command builder
Build a validated command from the pinned command inventory.
- While integratingAPI explorer
Browse every documented operation, parameter, and example.
- Choosing a modelProtocol comparison
A neutral, source-pinned comparison of Bitcoin metaprotocols.
Why they are local
Section titled “Why they are local”Anything you paste into a transaction tool is sensitive. An outpoint list reveals what you hold. A PSBT reveals what you are about to do. Sending either to a service to be analysed creates a record you did not need to create.
So these tools parse in the page. There is no upload, no analytics on the content, and no request made on your behalf.
What they are not
Section titled “What they are not”They are explanatory. They are not the active validator, and they do not replace validating a concrete transaction against the validator revision your counterparties run.
The allocation visualizer is the closest to authoritative, because it runs the same engine as the conformance vectors and the test suite. Even so, it models normal allocation from one pinned revision, not the live network you are about to broadcast to.