Entangled-State Explorer
The Entangled-State Explorer opens a machine's chain at the block level. The entangled state is a tamper-evident log over every transition of a machine, and this app lets you read it, add to it, and see exactly how it holds together.
How the blocks entangle
Each block is hash-linked to the one before it:
Because each hash folds in the previous hash, the payload, and the Zeqond it was sealed at, altering any block breaks every hash after it — the past can't be edited without the break being obvious. Blocks are sealed on the 1.287 Hz HulyaPulse, so each one is stamped to an exact tick of the clock.
What you can do
Load a machine
Enter a slug and fetch its chain blocks — the transitions and the recent events, in order.
Submit an event
Add an event to the chain and watch it seal into the next block.
Claim the window
Claim the next sealed window — the current 0.777-Zeqond slot the chain is filling.
Explorer vs. ledger vs. observer
Three apps read the same entangled state, framed for different jobs: the Explorer is the block-level view (the hashes and windows), the Ledger frames the same chain for audit and reconciliation, and the Observer is the live, scoped monitor. Same tamper-evident chain, three lenses.
Open it
Read next
- Proof of Elapsed Zeqonds — why sealing on the clock resists rewriting.
- State machines — the chain these blocks belong to.
- The Zeq envelope — the proof each transition carries.