Address watches

An address watch registers an on-chain address so you get the same balance, history, and webhook visibility you get on your own wallets — but for an address DFNS does not control. An address watch holds no key: it cannot sign or move funds. It is a pure, read-only registration. Use it to monitor addresses outside your custody: a counterparty’s account, an address you track for compliance or risk, or any public address you want event and balance visibility on — without running separate chain-watching infrastructure.

What you get

Once an address is watched, it plugs into the same indexer as your wallets:

Balances — GET /address-watches/{addressWatchId}/assets, the same surface as wallet balances.
History — GET /address-watches/{addressWatchId}/history, value transfers touching the address.
Decoded contract events — GET /address-watches/{addressWatchId}/blockchain-events.
Webhooks — address_watch.blockchain_event.transfer.confirmed fires when a transfer touching a watched address is confirmed on chain (for example, a deposit). See webhook events.

Create and manage

Create an address watch from the dashboard’s Watchlist tab, next to Wallets and Vaults (a name is required there), or via the API with POST /address-watches:

{
  "network": "Ethereum",
  "address": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"
}

name and externalId are optional. The response carries an aw-… id and a status of Active or Archived. Lifecycle:

One watch per address per network, per organization while it is Active. Different organizations can watch the same address independently.
Deleting a watch (DELETE /address-watches/{addressWatchId}) archives it (status: Archived) and immediately stops its webhooks. Watching the same address again on the same network reactivates the archived watch — same id, same history, same name/externalId.
Address watches count against your organization’s wallet limit; there is no separate quota.

Supported networks

Address watches are available on a broad set of networks — most EVM networks and Solana. Support is per-network: the network field accepts only networks where address watching is enabled. See the POST /address-watches request schema for the current list of supported networks rather than assuming a given network is covered.

Permissions

Three permissions gate address watches — see roles and permissions:

Permission	Grants
`AddressWatches:Create`	Create an address watch
`AddressWatches:Read`	List, get, and read a watch’s assets, history, and blockchain events
`AddressWatches:Delete`	Delete (archive) a watch

Create address watch

API reference for the address-watch endpoints

Webhook events

Subscribe to on-chain events for watched addresses

Introduction

Core Concepts

Platform Features

Networks

Solutions

Guides

Advanced

What you get

Create and manage

Supported networks

Permissions

Create address watch

Webhook events

​What you get

​Create and manage

​Supported networks

​Permissions

​Related

Create address watch

Webhook events

What you get

Create and manage

Supported networks

Permissions

Related