The Streams API provides two webhooks for each block that contains the event you are interested in.
​
One with confirmed: false when the transaction is initially mined and one with confirmed: true when the transaction is confirmed after a certain number of blocks. By understanding these webhooks and the number of confirmations required for your blockchain, you can effectively monitor and track your transactions.

When a block is initially mined, you will receive a webhook with confirmed: false. This webhook indicates that the transaction has been added to a block but has not yet been reached the number of block confirmations required. You can use this webhook to track the progress of the transaction and take necessary actions, such as sending notifications to users or updating a database.

Once the block is confirmed, you will receive a second webhook with confirmed: true. This webhook indicates that the transaction has been successfully executed and fulfilled the number of confirmations required by the network. The number of confirmations required varies based on the blockchain you are using.

To determine the number of confirmations required for your blockchain, please refer to the table below. You can find this information under the Confirmation Blocks column for each supported chain.

Until a block is confirmed, it is possible that a re-organization of the chain may occur, invalidating some information. If a re-organization does occur before a block is confirmed, the information associated with the block is deleted and the updated block is inserted in its place.