Skip to main content

Wallet & Transaction Scanner

This page exists for teams who want a simple rule of thumb:

  • if you are reviewing a contract, use Contract Scanner
  • if you are reviewing an action a wallet is about to sign, use Pre-Sign Preview & Wallet Risk Review
  • if you want Dralvia to route an input automatically, use the unified scan path

What this feature is really for​

Many smart contract teams receive mixed inputs:

  • a wallet address
  • a contract address
  • a transaction hash
  • calldata from a signing prompt

This feature is about routing those inputs into the right review path, not pretending every smart contract question is the same question.

The easiest way to think about it​

Contract question​

"What kind of contract is this, and what controls does it still have?"

Use:

Signing question​

"What is this wallet about to approve or sign?"

Use:

Mixed or uncertain input​

"I have a smart contract artifact but I am not sure which review surface is correct."

Use:

  • the unified scan path

Supported inputs​

Depending on your workflow, you may route:

  • wallet addresses
  • contract addresses
  • transaction hashes
  • encoded transaction calldata
  • mixed user-provided smart contract inputs through the unified scanner

What Dralvia tries to answer​

For wallet and transaction review, Dralvia focuses on practical decision questions:

  • Is the action granting spend or operator rights?
  • Is the destination contract calm, opaque, upgradeable, or risky?
  • Is the transaction meaning clear enough to approve?
  • Does the action need routine approval, manual review, or a stop decision?

Common workspace workflows​

Treasury approval workflow​

  1. Scan the contract.
  2. Review the exact wallet action in Pre-Sign Preview.
  3. Preserve the exported result before approval.

Trading or token workflow​

  1. Review contract posture first.
  2. Check token behavior and liquidity context.
  3. Review the specific approval or router interaction before signing.

SOC or incident workflow​

  1. Route the input into unified scan if the artifact type is unclear.
  2. Open the contract review if the artifact resolves to a contract.
  3. Open the wallet-risk review if the artifact resolves to a signing action.

Unified scan examples​

If you want Dralvia to route the input automatically:

  • GET /api/unified/scan?input=0x...&type=wallet&chain=Ethereum
  • GET /api/unified/scan?input=0x...&type=tx&chain=Ethereum

Guest-mode availability and workspace entitlements depend on the environment and enabled features.

What this page does not mean​

This page does not mean every wallet address or transaction hash gets the same depth as a full contract review or a live pre-sign action review.

The important idea is:

  • use the right tool for the right smart contract decision