opBNB transaction monitoring for BNB and BEP-20
Confirmed alerts on BNB Chain's OP Stack Layer 2
opBNB is BNB Chain's Layer 2 on the OP Stack, with low fees and fast blocks. Monitoring uses chain ID 204 — it is not BNB Smart Chain (56). Add a 0x wallet or contract address, pick listed tokens (native BNB today; BEP-20 when listed), and choose an HMAC-signed webhook or Telegram. transaction_confirmed waits for the network confirmation depth; optional transaction_detected fires when the transfer first appears in a block. Per-wallet notifySettings.onConfirmed and onDetected choose which events are sent. A BSC monitor will not see these transfers, even when the 0x address text matches.
What is specific to opBNB alerts
- When the alert is sent
- Chain ID is 204. The signed webhook is sent after the transfer is confirmed on opBNB, not from the mempool. Confirmed alerts wait for this network's confirmation depth — the payload includes confirmations and requiredConfirmations.
- Address format
- opBNB uses 0x addresses, like BNB Smart Chain, but the chains do not share balances. Create the monitor on opBNB, not BSC, or the transfer never matches.
- Tokens on this network
- Native BNB is listed for opBNB. The network uses BEP-20 for tokens; only assets listed for this network are monitored. A BSC monitor does not see opBNB transfers.
Example confirmed webhook
{
"eventType": "transaction_confirmed",
"data": {
"network": "opBNB",
"asset": "BNB",
"direction": "in",
"txHash": "0x…",
"from": "0x…",
"to": "0x…",
"confirmations": "<network confirmation depth>",
"requiredConfirmations": "<network confirmation depth>"
}
}Why teams monitor opBNB here
Low-fee opBNB wallet alerts
opBNB is built for cheap, frequent transfers. Set a USD amount filter so dust does not spend a credit.
BNB, BEP-20 and contract calls
Watch native BNB and BEP-20 transfers, including USDT when listed for opBNB, plus contract calls. The signed JSON schema matches other EVM networks.
HMAC webhooks or Telegram
Each wallet has notifySettings for webhook and Telegram channels, incoming or outgoing, onDetected or onConfirmed.
How opBNB monitoring works
Add your opBNB wallet
Enter the opBNB wallet address you want to monitor. We validate the address format automatically.
Configure alerts: native coins and BEP-20
Choose which tokens to track (native coins and BEP-20), set minimum amount thresholds, and specify your webhook URL.
Receive confirmed webhooks
Get a signed JSON webhook after a matching transaction is confirmed on opBNB. Pending mempool transactions are not sent.
Use cases for opBNB monitoring
Payment gateways — accept native coins and BEP-20 tokens on opBNB without running your own node.
Telegram bots & mini-apps — monitor deposits and trigger automated actions for opBNB wallets.
Custodial wallets — track thousands of opBNB deposit addresses from a single dashboard.
Personal alerts — get notified in Telegram when your opBNB wallet receives funds above your threshold.