For the person waiting
Paste your own deposit and leave the page open, or come back later: it remembers the list in this browser and shows what changed since you last looked.
✓ Your list stays in this browser · read-only
Waiting on a refund? Watch it here.
A deposit stuck in the Omni bridge moves in steps: the refund is requested, its lock runs out, someone executes it, the coin goes home. Paste the deposits you are waiting on. The page checks each one, re-checks every 10 minutes while it stays open, and tells you the moment one changes and what comes next.
How a watch round readsIllustration
ticket #4512Changed
Ready to refund
Was "Refund requested" at the last check. The lock has ended: one NEAR call sends the coin back to the refund address.
ticket #4519Same
Refund requested
Its lock ends on the date shown. Nothing to do until then.
For wallet and exchange support teams
Every stuck-deposit ticket, in one place
When a customer's ZEC or BTC never arrives through the Omni bridge, the fix is the bridge's own refund, and it takes days: a request, a lock, an execute. This page keeps watch so nobody has to re-check by hand.
- 1. Paste every open caseOne deposit hash per line, with the ticket number after it. The list is kept in this browser only, so it never reaches us or anyone else.
- 2. Leave the tab openEach deposit is re-checked every 10 minutes. A row that changed is marked, the tab title counts the changes, and the browser can notify you.
- 3. Copy a summary into the ticketOne button writes each deposit's state, why, and what changed, in plain words you can paste to the customer.
- 4. Tell the customer the exact next stepOpen any row for the full check: the steps, what each costs, and the only address the coin can go back to.
- Flag the ones that can't come backAbsorbed below the minimum, a placeholder refund address, too old to request, or behind the bridge's years-long lock: the page says so, so nobody promises a refund that can't happen.
Nothing leaves your browser
The list and the last states are saved in this browser only. Each check reads the same public sources as a single check (the chain's explorer, the Omni bridge indexer, NEAR), which see your IP address, as any website does.
It never moves coins
Watching is read-only. Requesting or executing a refund is a NEAR call you sign yourself, and the coin can only go back to the refund address the deposit names. Nobody needs a seed phrase or a key.