Tutorial 2 of 7
Investigate a transaction with a playbook
Beginner 7 min
Paste a transaction hash and addresses, let a playbook add the decoder, bridge, cross-chain and smart-account checks, and follow the suggested next steps.
Most investigations start with a hash in a chat message or a support ticket. Chainscope turns it into a set of checks in one step.
1. Paste what you have
Choose File → New case, then File → Paste addresses or hashes…. Paste the whole message — explorer pages, logs and CSV lines work too. Chainscope picks out:
- transaction hashes (
0x+ 64 hex characters), - addresses (
0x+ 40 hex characters), - Snapshot spaces such as
aavedao.eth.
Each match gets a row with a checkbox and a type (Transaction, Wallet, Contract, Token, DAO space). Entries that are already in the address book are greyed out. Choose the Chain for new entries — the tools cover Ethereum, Base, Arbitrum, Optimism, Polygon, Avalanche and BNB Chain.
Tick Add the matching playbook checks for each new entry and press Add to the case.
2. What the playbooks add
| Entry type | Playbook | Checks |
|---|---|---|
| Transaction | Investigate a transaction | Decode, Bridge status, Cross-chain path, Smart-account bundle |
| Contract or token | Contract due diligence | Upgrade control, Relationships |
| Wallet | Wallet risk review | Approvals, Aave health, Account type |
| DAO space | Governance review | Governance |
You can apply a playbook later from the Address book tab with the buttons in the Actions column.
3. Run everything
Press Run all (or Ctrl+Shift+Enter). Every check is one request to the usefulweb.site tool API; the status bar counts along, and when the API rate limit is reached the check shows Waiting for the tool API rate limit: … s and continues by itself. Stop run all in the status bar cancels the rest.
A check that finds nothing is still useful: No supported bridge deposit (CCTP, Across, OP Stack or Arbitrum canonical) was found in this transaction. tells you the funds never left the chain through a supported bridge.
4. Read one check
Select Decode … in the list on the left. The Result card shows the tool's summary, metrics such as Status, Function, Token transfers and Fee (native coin), and the findings — for example The transaction 0x… reverted: it paid the gas fee but changed nothing on chain. Full tool output shows every table of the tool, including the decoded events and token transfers.
Addresses and transactions in this result lists everything the decoder returned with its role (sender, called contract, token receiver). Add puts an entry into the address book; label it there so it is named in every later result.
5. Follow the suggestions
A decoded transaction suggests three next checks: MEV in block … (was it sandwiched?), Upgrade control of … for the called contract, and Bridge status of … when tokens moved. Press Add check, then Run check. If the MEV explorer finds that the block's sandwich hit a transaction from your address book, the finding is critical: The case transaction … was sandwiched by ….
Ready to try it?