Tutorial 4 of 7
Bridges, cross-chain paths and pasted data
Intermediate 6 min
Track a CCTP transfer from Ethereum to Base, understand the bridge statuses, and switch checks between live look-ups and pasted receipts, logs or bytecode.
"I bridged my USDC and it is not there" is one of the most common web3 support questions. Chainscope combines the Bridge Transfer Tracker, the Cross-Chain Transaction Explorer and the Transaction Decoder for it.
1. The sample case
Open File → Templates… → Where is my bridged USDC? (sample data). It uses the tools' offline example logs of a Circle CCTP burn of 250 USDC from Ethereum to Base. After the run you see the same finding twice:
The circle-cctp-v1 transfer of 250 USDC to Base was decoded from pasted logs; its delivery was not checked.
Pasted logs contain the deposit but not the destination chain, so delivery cannot be confirmed — Chainscope says so instead of guessing.
2. What the statuses mean
| Finding level | Bridge status | Meaning |
|---|---|---|
| Pass | completed | The destination transaction was found. |
| Medium | pending | The deposit is on the source chain; nothing arrived yet. |
| Medium | awaiting-attestation | CCTP is waiting for Circle's attestation before the mint. |
| Low | unknown | The tool could not tell. |
| Info | not-trackable / offline | Recognised, but delivery cannot be checked automatically. |
When the destination transaction is known, the result suggests Decode … on the destination chain, so you can see exactly what the recipient received.
3. Switch to your own transfer
Select Bridge deposit in the source transaction. The form has Source chain (where you sent from) and Source transaction hash; the pasted logs live under More options. Paste your hash, empty the logs field and press Run check. For the cross-chain check change Data source to Look up a hash.
While you type, the Run card shows what is still missing (Enter the transaction hash to look up.) and marks the check Inputs changed since the last run once you edit it after a run.
4. Pasted data elsewhere
Most checks have a Data source choice. Pasted modes need no chain access — the tool API decodes what you paste:
- Transaction Decoder: pasted calldata, optionally with a function signature or an ABI.
- Contract Upgrade Explorer / Relationship Graph: runtime bytecode.
- Incident Replay: receipts JSON of up to five transactions.
- Wallet Permission Explorer: Approval and ApprovalForAll logs.
- MEV Explorer / Rollup Batch Explorer: block JSON.
This is how you analyse archived incidents, exports from your own node or data from a private chain fork.
5. Offline
Without a connection every run says You are offline. Every check needs the usefulweb.site tool API; try again when you are connected. Your case, earlier results, the graph, the timeline and the report remain readable, and the full tool output of earlier runs is cached in this browser.
Next: batch runs and history.
Ready to try it?