Watchlists & Private Tags

Personalize the explorer: watch addresses, label what matters, and decode the contracts you care about.

Account features make the explorer yours. Watchlists notify you about activity, private tags replace opaque hashes with your own labels, and custom ABIs decode contracts that aren’t publicly verified — all visible only to your account.

Watchlists

A watchlist entry monitors one address. When it sends or receives funds matching your filters, you get notified by email and/or webhook.

Add from the UI

Open any address page on xdcscan.io and click Watch. Choose which transfer types trigger notifications:

• Native coin — incoming and/or outgoing
• ERC-20 tokens
• ERC-721 and ERC-1155 NFTs

Manage via API

curl -X POST https://xdcscan.io/account/api/v1/user/watchlist \
  -H "Authorization: Bearer $OPENSCAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "address_hash": "0x1234567890abcdef1234567890abcdef12345678",
    "name": "Treasury wallet",
    "notification_settings": {
      "native": { "incoming": true, "outgoing": true }
    },
    "notification_methods": { "email": true, "webhook": true }
  }'

Webhook delivery details and payload format: Alerts & Webhooks.

Good uses for watchlists

• Treasury and cold-wallet monitoring
• Watching deployer wallets of contracts you integrate with
• Tracking bridge or oracle contracts for operational awareness

Private tags

Tags attach your own labels to addresses and transactions. Once tagged, the label replaces the hash across the explorer UI — in search results, transaction lists, and address pages — but only for your account.

curl -X POST https://xdcscan.io/account/api/v1/user/tags/address \
  -H "Authorization: Bearer $OPENSCAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "address_hash": "0x1234567890abcdef1234567890abcdef12345678",
    "name": "Treasury wallet"
  }'

Tags are private by design. Public naming (shown to everyone) comes from verified token metadata and project submissions, not account tags.

Custom ABIs

Public decoding requires public verification. When that’s not possible — the contract isn’t yours, or the build settings are lost — upload the ABI to your account and the explorer decodes methods, inputs, and events for your views:

curl -X POST https://xdcscan.io/account/api/v1/user/custom-abis \
  -H "Authorization: Bearer $OPENSCAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "contract_address_hash": "0xabcdefabcdefabcdefabcdefabcdefabcdefabcd",
    "name": "MyContract",
    "abi": "[{\"type\":\"function\",\"name\":\"balanceOf\",\"inputs\":[{\"name\":\"account\",\"type\":\"address\"}],\"outputs\":[{\"name\":\"\",\"type\":\"uint256\"}],\"stateMutability\":\"view\"}]"
  }'

If you do own the contract, verify it publicly instead — everyone benefits. See Contract Verification.

API keys

The same account page issues API keys that raise your REST API rate limits. Full details: API Keys & Rate Limits.

Data and privacy

• Watchlists, tags, and custom ABIs are tied to your account and never shown to other users.
• Deleting your account removes all of them permanently.
• All endpoints above are documented in the Account API.