https://sandbox-explorer.stridge.com

Never build an Etherscan, Tronscan, Solscan, or other public explorer link from a sandbox transaction hash or address. On the real chain you find nothing, or a different object.

What you can see

The simulated chains are shared by every sandbox, so their raw facts are public. Without signing in you can browse:

• the simulated networks, each with its latest block and whether it is live, paused, or stalled;
• blocks, newest first, and any block by height or hash;
• transactions, newest first, and any transaction by hash, with every party and transfer in it;
• any address, with its on-chain balances and activity;
• search by transaction hash, address, or block height.

The public view tells nothing about any sandbox: it does not say which sandbox a transaction or address belongs to.

Signing in

Signed in, the explorer also shows your part in the chain: which transactions and addresses belong to your sandbox, the Stridge object each one belongs to (a deposit, settlement, routing, payout, or transfer), the simulation that caused it, and each object's legs in time order.

You sign in from the dashboard. In your sandbox, every transaction hash, address, and block the dashboard shows links to the explorer. Opening one hands your dashboard session to the explorer and signs you in to that sandbox, read-only. There is no separate explorer password.

The explorer's access follows your dashboard session: sign out of the dashboard, or lose access to the workspace, and the explorer stops showing your sandbox's details.

Links in API responses and webhooks

In the sandbox, scanner_url on deposits and on deposit.confirmed webhooks links the transaction in the sandbox explorer:

https://sandbox-explorer.stridge.com/60/tx/0x9c1e…4b7a?in=acme

The path is the network_id and the transaction hash. in names your workspace, so a signed-in reader lands on the right sandbox. Store the link as given rather than building it yourself. scanner_url is an empty string where no explorer link is available.

In live, scanner_url links the chain's public block explorer instead.

After a reset

A reset empties your sandbox, but the chain keeps its history. Transactions from before the reset stay on the public chain and in your signed-in view, marked as from before the reset. Your sandbox's activity list shows only what happened since the last reset.

Limits

Public reads are rate limited per client address, and a page shows at most 50 rows. Search terms are limited to 128 characters.