Watched addresses
The following addresses are tracked for balance changes and transaction activity. Each is a well-known Bitcoin address with publicly attributed ownership.
| Label | Category | Address |
|---|---|---|
| Satoshi (Genesis) | Historic | 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa |
| Binance Cold | Exchange | 34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo |
| Bitfinex Cold | Exchange | bc1qgdjqv0av3q56jvd82tkdjpy7gdp9ut8tlqmgrpmv24sq90ecnvqqjwvw97 |
| Kraken Cold | Exchange | bc1qr4dl5wa7kl8yu792dceg9z5knl2gkn220lk7a9 |
Transaction direction (IN / OUT)
Each transaction's direction is computed from its net satoshi effect on the watched address. If the address receives more satoshis from the transaction's outputs than it spends via inputs, the direction is IN. If it spends more than it receives, the direction is OUT. This calculation uses integer satoshi arithmetic internally (no floating-point) to avoid rounding errors.
Confirmation state
Transactions are labeled either PENDING (in the mempool, zero confirmations) or CONFIRMED (included in a mined block). The block height is shown for confirmed transactions. Pending transactions may be dropped from the mempool if they remain unconfirmed for an extended period, in which case they will disappear from this list.
Deduplication
When a single transaction involves multiple watched addresses (for example, a transfer between two tracked exchange wallets), the transaction appears only once with all affected addresses listed. This prevents the same transaction from cluttering the feed.
Data source and caching
Transaction data is fetched from the mempool.space /api/address/{address}/txs endpoint for each watched address. Requests are staggered 50ms apart to stay within rate limits. Results are cached server-side for 60 seconds.
Balance data comes from a separate call to the address summary endpoint and is also cached for 60 seconds. Both datasets refresh independently — a momentary mismatch between the balance shown and the latest transaction is normal during the cache window.
Limitations
- Only the 20 most recent transactions across all watched addresses are shown. Older history can be viewed on mempool.space directly via the address links.
- The BTC amount shown is the net effect on the watched address, not the total transaction value. A transaction that moves 100 BTC but only sends 0.5 BTC to a watched address will show 0.5 BTC.
- Pending transactions are snapshots of the mempool at fetch time. Transactions that are replaced (RBF) or evicted will disappear without notice.