MXEs
Application-owned encrypted environments. Explorer groups programs, definitions, and computations around the MXE that owns them.
A concise guide to Arcium Network concepts as they appear in Arcium Explorer.
Arcium lets Solana applications coordinate encrypted computation with MPC, so inputs can stay hidden from any single node while execution is still anchored onchain.
Arcium Explorer follows the public network objects behind that flow: MXEs, computation definitions, computations, clusters, Arx nodes, and transactions. For protocol background, start with the Arcium docs intro and the basic concepts.
Live mainnet stats are temporarily unavailable. The concept guide and docs links remain available.
Application-owned encrypted environments. Explorer groups programs, definitions, and computations around the MXE that owns them.
Reusable circuit descriptions. They tell the network what encrypted computation can run and how much Arcium CU it requires.
Submitted work items. A computation moves from queued to finalized or failed as the network executes it and records the result.
Execution capacity. Clusters coordinate sets of Arx nodes, and nodes contribute capacity to encrypted computation.
An MXE is an MPC eXecution Environment: the encrypted execution environment that owns computation definitions and submitted computations for an application.
A computation definition describes the circuit interface, expected inputs and outputs, and Arcium CU amount used when computations are submitted.
Clusters group Arx nodes that participate in encrypted computation, so they explain where network capacity and execution responsibility sit.