Independent read-only explorer

Tacit/Dualscan both chains, one page

loading

Bitcoin envelopes and the asset registry, the confidential pool on Ethereum, the EVM pools on Base, Robinhood Chain and MegaETH, the secondary market, and the bridge that folds one into the other. Every panel is read from Tacit's public API, its chain keepers and mempool.space — no wallet, no sign-in, no mock data. Two routes (/assets, /market) answer cross-origin only for tacit.finance, so those panels carry a dated snapshot, labeled where they appear. Sources and limits are listed at the bottom.

Bitcoin assets
–
registry
Notes live
–
confidential pool
Bridge burns
–
Bitcoin → EVM
Bridge mints
–
proven and paid
EVM pool notes
–
all chains combined
Relay
–
state

01 · The bridge

reading…
Bitcoin burns
–
assets burned on Bitcoin, folded by reflection
in flight–
EVM mints
–
notes minted after their proofs landed

–

Bitcoin reflection

folded to height
–
relay confirms
–
network tip (mempool)
–
relay vs network
–
cross-outs folded
–

Burn deposits

deposits seen
–
awaiting bundle
–
oldest awaiting
–
consumed
–
updated
–

Bridge proofs

relay state
–
proving
–
settling
–
failed (1h)
–
heartbeat age
–

A burn on Bitcoin becomes a note on the EVM side only after reflection folds its block and a proof is minted. The gap between burns and mints is work in flight, not a missing payment: check –.

02 · Bitcoin side

reading…

Assets etched

–
in the registry snapshot

Envelope records

–
snapshot · etches + mints + burns

Newest record

–
 

Fee now

–
sats/vB

Asset registry

TickerEtched at heightMintsBurnsHolders24h satsTransfers
loading…

Registry captured from /assets on api.tacit.finance; that route answers cross-origin only for tacit.finance, so this page ships the response as a dated snapshot rather than bypassing it. Open the live endpoint for the authoritative current list.

Newest envelope records

etches, mints, burns
  • –loading…

Transfers inside the Bitcoin pool are Taproot envelopes; tacitscan decodes those. This page shows the registry's etch/mint/burn records plus the live fee market, and never invents a transfer.

TAC — the protocol asset

supply
21,000,000 TAC (fixed)
genesis (etch)
height 948,242
asset id
f0bbe868…3f94762b
Ethereum ERC-20
0xA1313e…8279
genesis tx
e2d10be1…ca481e

Published deployment facts from Tacit's DEPLOYMENTS.md. The supply is an on-chain commitment; the opening is pinned on IPFS so anyone can re-derive it from the chain alone.

03 · Ethereum confidential pool

reading…

Pool 0x000000000Ed1eabD231Be41d93b719056F7febFC — immutable, no proxy, no pause switch. Counts below are the indexer's stream, not our own scan.

Leaves

–
notes ever committed

Nullifiers

–
notes spent

Wraps

–
deposits into the pool

Cross-outs

–
moved to another chain

Recent pool ops

  • –loading…

From /confidential/index, newest first. Each op links to its Ethereum transaction. Amounts, owners and memo contents are not published here.

Relay

state
–
proving
–
settling
–
failing (1h)
–
age
–
open board
–

Prover board

queued / claimed
– / –
proved / failed
– / –
wait p50/p90
–
prove p50/p90
–
workers
–

04 · EVM pools

reading…

The same pool contract address on every chain — 0x000000c2A20657CE25f2Ba99737933D031AFBEE9 — with an independent note tree and keeper per chain. Sizes are the keeper's live head.

ChainChain idPoolNotesPendingRoot (head)Fee
loading…

Base activity

  • –loading…

Confirmed Transact/Received events the Base keeper publishes, last ~300 blocks. Links go to Basescan.

Canonical bridged tokens (Ethereum)

TokenAddress
TAC0xA1313e…8279
tacBTC (cBTC)0xdf1d99…D696
tacUSD (cUSD)0x23cACF…1564

Each canonical ERC20 is minted only by the pool. Addresses from Tacit's DEPLOYMENTS.md; balances are not shown because this page reads no wallet.

05 · Bitcoin pools & secondary market

reading…

Pools are initialised per asset on Bitcoin; the market is where holders list notes for sale in sats. Both come from /pools and /market, captured as a dated snapshot with the registry.

Pools initialised

–
pool_init records

Notes in pools

–
leaves committed

Listings open

–
–

Init proofs verified

–
as published in the feed

Pools

denomination in sats
AssetDenomLeaves / spentInit heightPool init tx
loading…

Market records

KindRecordsPricedExpiry
loading…

Amounts are base-unit integers exactly as the API publishes them; no market price is implied and no listing is endorsed. init_sig_verified is the feed's own field — this page reports it and does not re-verify a signature itself.

06 · The privacy boundary

what this page can and cannot see

Public on chain — and shown here

  • Timing, block heights, transaction hashes and fees of every pool op.
  • Pool roots and note-tree sizes per chain.
  • Each note commitment and, once spent, its nullifier — a nullifier proves a note was spent without saying which.
  • Wrap and cross-out envelopes: the asset id and the public amount that entered the pool.
  • Points and the public leaderboard, which are keyed by address by design.

Stays hidden — this page does not pretend otherwise

  • Amounts and owners of notes once inside the pool; a transfer reveals neither side.
  • Links between notes: an observer sees counts and timing, not who paid whom.
  • Memo contents — they are ciphertext in the events this page reads.
  • Your keys, notes and balances: there is no wallet here, and no request leaves your browser except the source fetches listed below.
  • What the relay sees when you use it (your IP and the ops it proves) is a property of the relay, not of a block explorer.

Honesty note: this explorer reads a public API from your browser, so that API sees your IP and which panels you load. It cannot link that to a wallet, because it never asks for one.

07 · Look up a footprint

tacit1 address · Bitcoin txid · EVM address

What is public about an EVM address: its points, deposits and claim. About a Bitcoin txid: its block, fee and outputs. About a tacit1… address: its network, version, flags and lanes — the address itself carries no balance. Nothing you type is stored or sent anywhere except the source named for that lookup.