How Should Businesses Monitor On-Chain Transaction Status?
How should businesses monitor on-chain transaction status? From sending to final settlement, a transaction goes through several stages: signed, broadcast, waiting in the mempool, included in a block, and reaching enough confirmations. Along the way it can also fail, be replaced or be dropped. Businesses need to track these states for every transaction, set confirmation standards per chain, alert promptly on long-unconfirmed transactions, failed executions, unexpected replacements and chain reorganizations, and update business systems based on final status.
What States Can an On-Chain Transaction Be In?
After signing, a transaction is broadcast to the network and queues in nodes’ mempools. Once included in a block it has its first confirmation, and each additional block adds another; it is only truly complete after reaching the required number of confirmations or the chain’s finality standard. Abnormal cases include failed broadcasts, transactions that go unincluded for a long time, transactions replaced by another one using the same nonce or the same UTXOs, and transactions dropped from the mempool. On EVM chains, note that inclusion does not mean success: a transaction whose contract execution fails is still recorded on-chain and still pays gas, so check the execution result in the receipt.
How Many Confirmations Does Each Chain Need?
The more confirmations, the less likely a transaction is to be rolled back by a chain reorganization. Bitcoin has no absolute finality; a common practice is to wait for 6 confirmations, and more for larger amounts. Since moving to proof of stake, Ethereum has explicit finality, with blocks marked finalized after roughly two epochs, a little over ten minutes. Other chains have their own confirmation rules. Businesses should set crediting standards by chain and amount, show user deposits as “processing” until they meet the standard, and screen the source of funds with KYT at the same time.
Which Situations Should Trigger Alerts?
Transactions that stay unconfirmed for a long time should trigger an alert and a possible speed-up, and failed executions should trigger an alert and an investigation. The most important thing to watch for is a replacement your own system did not initiate: if a transaction is replaced by an unknown transaction using the same nonce or UTXOs, someone else can sign for that address, and it should be treated as a security incident under your crypto incident response plan. When a confirmed transaction disappears because of a reorganization, reverse any deposits already credited, or resend withdrawals that were marked complete.
How Should Transaction Status Connect to Business Systems?
Typically, the wallet system notifies business systems through callbacks when a status changes. Callbacks can arrive more than once or out of order, so business systems should handle them idempotently by transaction hash and only credit funds or mark completion once a final state is reached. When a transaction is replaced, link the business record to the hash that was finally confirmed. Regular reconciliation then checks on-chain status against business records in full, catching any missed callbacks.
Conclusion
Monitoring on-chain transaction status means tracking every stage from broadcast to final settlement, setting confirmation standards by chain and amount, alerting promptly on unconfirmed, failed, unexpectedly replaced and reorganized transactions, and reliably syncing final status to business systems. Safeheron’s Wallet-as-a-Service provides businesses with MPC key management and a policy engine.
Want full visibility into every on-chain transaction your business makes? Contact Safeheron’s Sales Team to Book a 1:1 Demo
Looking for a secure way to manage digital assets?
Talk to our experts and find the right solution for your business.
Request a DemoLooking for a secure way to manage digital assets?
Talk to our experts and find the right solution for your business.