METADATA SCANNER

—

Media packed token scanner. Is it truly onchain?

Paste a contract address. First we tell you if it is a token, an NFT, a wallet, or nothing on-chain. Then we tell you if the image, audio, or game is stored on the token, or only linked off-chain.

Detects token, NFT, wallet, or nothing on-chain.

Waiting for a contract address. We will say what the account is before we grade any media.

  • G0Off-chain file. No usable pointer and no packed bytes. Typical HTTP/IPFS/Arweave fetch.
  • G1On-chain metadata, off-chain file. Name, symbol, and uri sit on the mint. The uri is still HTTP, IPFS, or Arweave.
  • G2Ledger-packed artifact. Bytes in a memo or instruction of a confirmed tx, not copied into the mint.
  • G3Inscription on linked mint. This CA’s URI is HTTP/IPFS. A companion mint holds the packed data: file.
  • G4On-mint file. This mint’s uri or additionalMetadata is a data: URI. Rent pays for a couple of KB.
  • G5Fully on-chain file. AnyScribe program account (Fn7ASHW…) with ANYSCRIB header, published, mint-bound. HTTP is a gateway onto RPC dataSlice, not the store.

Color runs dim to bright: gray is a link, sand is a transaction blob, sage is a linked mint, green is the file in this mint. v1 is a transaction format, not a file.