Inspect an Atomical
Read identity, location, history, and sealed state, and know which of the four you are actually looking at.
Universe implementation Verified 2026-08-31
Describes what a Bitcoin Universe service actually does today. It is not a statement about the protocol in general.
- Page ID
-
guides/inspect-an-atomical - Normative authority
- Universe implementation documentation
- Networks
- mainnet
- Documentation version
- 2026.08
- Audience
- everyone, holder, developer
- Owner
- bitcoin-universe-docs
- Sources
-
- Universe Atomicals NFT, Realm, and Subrealm index
at
1d9109c68d95private repository - Atomicals JavaScript CLI
at
1333565efbfe
- Universe Atomicals NFT, Realm, and Subrealm index
at
Esta página aún no está disponible en tu idioma.
Before you start
Section titled “Before you start”- Supported networks: mainnet.
- Status: Universe implementation for the read model, protocol behavior for the underlying facts.
- Read only.
What you need
Section titled “What you need”The Atomical ID, in the form <txid>i<index>. If you only have a name, resolve it first.
See inspect a ticker.
The procedure
Section titled “The procedure”- Read the asset by Atomical ID.
- Confirm the type and subtype. A plain NFT, a Realm, a Subrealm, a Container, and a DMINT item are different things.
- Read the current location and owner script.
- Read the history. Look at what changed and when, not only at the current state.
- Check the sealed flag. Unsealed state can change.
- Read the metadata, and treat every field as unverified.
- Record the generation identifier and indexed height.
Reference CLI equivalents
Section titled “Reference CLI equivalents”| Command | Reads |
|---|---|
get |
The Atomical |
location |
Current location |
state and state-history |
State, now and over time |
tx-history |
Transaction history |
at-location |
What is at an outpoint |
ftinfo |
Fungible token details |
See the CLI reference.
What to be careful about
Section titled “What to be careful about”- The number is not the identity. Key on the Atomical ID.
- Metadata proves nothing. See metadata trust.
- A media file is hostile input. Do not render it in a trusted context.
- A name in the payload is not the name it won. Resolve names separately.
If you are about to act on what you read, re-read at a current generation immediately before acting. A location read minutes ago can be stale.