--- title: "RadixScan" path: "/ecosystem/radixscan" bannerImage: "https://j9ytchrzkvqpcul7.public.blob.vercel-storage.com/03b0713d-8bbc-4b1d-8f9c-c28e3f460d5a.avif" version: "3.0.1" author: "ShardSpace Admin" createdAt: "2026-02-06T16:07:56.294Z" updatedAt: "2026-07-30T07:25:18.805Z" --- # RadixScan | **Type** | Community-run [Radix](https://www.radixdlt.com) network explorer, staking interface, developer console and AI agent layer | | **Status** | ๐ŸŸข Active | | **Operators** | Michael (Vorarlberg, Austria) and Leo (Rio de Janeiro, Brazil), who run the Emmoglu Stakery [validator](/contents/tech/core-concepts/validator-nodes) | | **Founded** | February 2023 | | **Deployments** | [dashboard](https://dashboard.radixscan.io) ยท [console](https://console.radixscan.io) ยท [sandbox](https://sandbox.radixscan.io) ยท [agent layer](https://ai.radixscan.io) | | **Hosts** | The Radix Dashboard, Developer Console and Sandbox โ€” `dashboard.radixdlt.com` and `console.radixdlt.com` redirect here (verified 30 July 2026) | | **Upstream** | [radixdlt/dapps-monorepo](https://github.com/radixdlt/dapps-monorepo) (Apache-2.0) | | **Website** | [radixscan.io](https://radixscan.io) | **RadixScan** is a community-run web service for the [Radix](https://www.radixdlt.com) network, started in February 2023 by two validator operators as an explorer and reporting tool. As of 30 July 2026 it also hosts the deployments that Radix's own first-party web applications resolve to: `dashboard.radixdlt.com` and `console.radixdlt.com` both redirect to RadixScan-operated instances of the [open-source dApps monorepo](https://github.com/radixdlt/dapps-monorepo). That makes RadixScan the de-facto home of the network's Dashboard, Developer Console and Sandbox, following the [Radix Foundation](/ecosystem/radix-foundation)'s [move to maintenance mode](https://www.radixdlt.com/blog/foundation-update-moving-to-maintenance-mode) in April 2026. ## Hosting the Radix Dashboard, Console and Sandbox The three first-party Radix web dApps โ€” the **Dashboard** (network explorer and staking interface), the **Developer Console** (package deployment, raw manifest submission, dApp-definition setup) and the **Sandbox** (a dApp frontend simulator for wallet requests) โ€” are no longer served from `radixdlt.com`. Resolved with a browser user agent on 30 July 2026: | `dashboard.radixdlt.com` | HTTP 302 โ†’ [dashboard.radixscan.io](https://dashboard.radixscan.io), path preserved | | `console.radixdlt.com` | HTTP 302 โ†’ [console.radixscan.io](https://console.radixscan.io), path preserved | | `sandbox.radixdlt.com` | No DNS record; [sandbox.radixscan.io](https://sandbox.radixscan.io) serves the app | | `stokenet-dashboard.radixdlt.com` | HTTP 302 โ†’ `dashboard.radixscan.io/` โ€” network *and* path dropped | | `stokenet-console.radixdlt.com` | HTTP 530 (Cloudflare edge, no origin) | | `stokenet-sandbox.radixdlt.com` | HTTP 530 | | `radixscan.com` | HTTP 302 โ†’ `dashboard.radixscan.io` | Deep links survive the mainnet redirects intact: a validator page, a resource page or a transaction summary under `dashboard.radixdlt.com` arrives at the same route on `dashboard.radixscan.io`, and `console.radixdlt.com/deploy-package` reaches `console.radixscan.io/deploy-package`. Nothing a reader clicks is broken โ€” but the destination is a community deployment, not a Radix-operated one. The redirects are issued from `radixdlt.com`'s own edge, which only the domain holder can configure, so the handover was made deliberately rather than through a lapsed domain. No public announcement of it has been found; the redirects themselves and the upstream commit record below are the evidence. ## How the handover was made possible All three apps live in [radixdlt/dapps-monorepo](https://github.com/radixdlt/dapps-monorepo) (Apache-2.0, SvelteKit, one `apps/` directory each for `dashboard`, `console` and `sandbox`). Three merged changes in the first quarter of 2026 turned it from something only RDX Works could deploy into something anyone can: - [#1034](https://github.com/radixdlt/dapps-monorepo/pull/1034) (11 February 2026) removed the PostgreSQL dependency and the bookmarked-validators feature that needed it, leaving the apps with no server-side database. - [#1035](https://github.com/radixdlt/dapps-monorepo/pull/1035) (11 March 2026) added a deployment guide to the README: environment variables, the default `@sveltejs/adapter-node` build, and step-by-step Vercel instructions. - [#1036](https://github.com/radixdlt/dapps-monorepo/pull/1036) (13 March 2026) made the dApp definition configurable, so an operator points an instance at their own on-ledger dApp definition instead of Radix's. The published configuration surface is four public environment variables โ€” `PUBLIC_NETWORK_NAME` (for example `mainnet` or `stokenet`), `PUBLIC_DAPP_DEFINITION_ADDRESS`, `PUBLIC_AMPLITUDE_API_KEY` and `PUBLIC_APP_ENV`. `packages/ui/src/network.ts` reads the first two and, when a definition address is supplied, substitutes it for both the console and dashboard defaults; leaving it empty falls back to Radix's own addresses, which the README warns "do not point to your front-end and will cause errors". [Gateway](/contents/tech/core-protocols/radix-gateway-api) endpoints for each network are carried in `packages/ui/src/constants.ts`, so no gateway of your own is required. The repository's last commit is 13 March 2026 and its README still lists the Stokenet URLs as if they were live. ## Stokenet has no hosted Dashboard or Console The redirects cover mainnet only. `stokenet-console.radixdlt.com` and `stokenet-sandbox.radixdlt.com` return HTTP 530 from the Cloudflare edge with no origin behind them, `stokenet-dashboard.radixdlt.com` lands on the *mainnet* dashboard homepage with both the network and the requested path discarded, and no `stokenet-` hostname resolves under `radixscan.io`. A developer working on [Stokenet](/contents/tech/releases/stokenet) therefore has no hosted explorer or console. The documented substitute is to run one: clone the monorepo, set `PUBLIC_NETWORK_NAME=stokenet` and a Stokenet dApp definition address, then either `npx turbo run build --filter=console` and `node apps/console/build` (Node, port 3000), or deploy `apps/console` on Vercel after swapping `@sveltejs/adapter-node` for `@sveltejs/adapter-vercel`. The [dApp Definition Setup guide](https://docs.radixdlt.com/docs/dapp-definition-setup) covers creating the definition account itself. ## RadixScan's own services Alongside the hosted dApps, RadixScan has run its own tooling since 2023: - **Archive node.** The Emmoglu Stakery archive node, opened for third-party queries as well as powering RadixScan's own reporting. - **Stake exporter.** A paid report (1 XRD at launch) analysing a staking address, with the result published to IPFS and the link returned to the requester in an encrypted message. - **Transaction exporter.** Bulk export of an account's transaction history, aimed at accounting and tax reporting. Data partnerships were announced with [RadixCharts](/ecosystem/radixcharts), [Xidar](/ecosystem/xidar), [Radix List](/ecosystem/radix-list), [XRD Domains](/ecosystem/xrd-domains), [Hermes Protocol](/ecosystem/hermes-protocol), [Z3US](/ecosystem/z3us), Radix Talk and this wiki. Several of those projects are now dormant or closed; the pages linked here record their status. ## Agent layer RadixScan also operates [ai.radixscan.io](https://ai.radixscan.io), a keyless [Model Context Protocol](https://modelcontextprotocol.io) server at `mcp.ai.radixscan.io` that lets an AI agent read ledger state and build, validate and simulate [transaction manifests](/contents/tech/core-protocols/transaction-manifests), then request a signature from the user's wallet โ€” the server holds no keys. It is covered in detail on [AI Agents and x402](/developers/ai-agents/ai-agents-and-x402). ## History and operators RadixScan was started by Michael, from Vorarlberg in Austria, who followed crypto from 2015 and began the project on the strength of Radix's prospects. Leo, from Rio de Janeiro, joined after meeting him in the Radix community; the two took part in the Cassandra tests and went on to run the Emmoglu Stakery [validator](/contents/tech/core-concepts/validator-nodes) together after the Betanet phase. The `radixscan.com` domain was gifted to them by Wylie of [Radnode](/ecosystem/radnode) and [XRD Domains](/ecosystem/xrd-domains); it now redirects to the RadixScan dashboard. ## External Links - [RadixScan](https://radixscan.io) - [RadixScan Dashboard โ€” explorer and staking](https://dashboard.radixscan.io) - [RadixScan Developer Console](https://console.radixscan.io) - [RadixScan Sandbox](https://sandbox.radixscan.io) - [RadixScan Agent Layer](https://ai.radixscan.io) - [radixdlt/dapps-monorepo โ€” the source of all three hosted dApps](https://github.com/radixdlt/dapps-monorepo) - [@RadixScan on X](https://x.com/RadixScan)