radixscan.io

Authoritatively validate a transaction manifest with the Radix Engine Toolkit.

Build a transfer manifest (keyless) moving fungibles and/or NFTs from one account to another.

Simulate a transaction manifest against the network without signing or submitting it.

Build a transaction manifest (keyless) from a structured step array — you never write manifest syntax.

Explain in plain language what a transaction manifest does, step by step — the human-readable basis for confirming a signature.

Identify any Radix address: its entity type, name and basic metadata.

Read a fungible or non-fungible resource: name, symbol, icon, divisibility, total supply and its authorities — who may mint, burn, freeze or recall it (with the gating badge), plus neutral factual flags (supply_fixed, mintable, freezable, recallable, rules_locked).

Read an account: fungible balances and NFT holdings (each NFT collection lists the held local ids, not just a count).

Read a validator: registration status, fee, total staked XRD, uptime, website, and its stake-unit (LSU) and claim-NFT resource addresses.

List a network's validators ranked by stake, each with its effective fee (reconciled against the current epoch, like radix_get_validator) and uptime.

Read a committed transaction: status, fee, classification, per-entity balance changes and the decompiled manifest.

List recent committed transactions on a Radix network, newest first — network-wide, or scoped to one entity via "address".

Read the current on-ledger state of a component: every stored field, SBOR-decoded with field names — e.g.

Read the entries of a Scrypto KeyValueStore — the storage behind the internal_keyvaluestore_ references that radix_get_component_state lists under key_value_stores (e.g.

Read non-fungibles (NFTs) of a resource.

List the accounts/components that hold a resource, sorted by holding descending — so the first page is the top holders.

Find the on-ledger entities a badge controls: given a badge resource (optionally a specific NFT local id), list every component, resource, pool or locker that names that badge as a role requirement — i.e.

Discover the callable interface of a package or component: every function and method of its blueprint(s) with access requirements (public vs role-protected — which calls need a badge proof) — the Radix equivalent of reading a contract ABI.

Start here to build a transaction.

List every manifest instruction with a one-line summary.

Detailed description of one manifest instruction (syntax and arguments); set examples=true for code samples.

List ready-made manifest templates (transfer, stake, unstake, claim, mint, burn, swap) plus the placeholder convention.

Return one manifest template: its body with {PLACEHOLDER} slots plus how to fill them.

Discover other agent-facing entries in the Radix ecosystem — agent MCP servers (e.g.

Look up the canonical on-ledger address of a well-known Radix entity (token, dApp component) by name or symbol — the inverse of radix_resolve_address, for when you have a name but not an address.

Request a human signature for a transaction manifest (non-custodial, human-in-the-loop).

Check the status of a signing request created by radix_request_signature.