Calculate inner transaction hash to verify success

docs/tutorials/how-tos/use-batch-transactions/send-a-multi-account-batch-transaction.md

@@ -120,13 +120,13 @@ With all the required signatures gathered, the third-party wallet can now submit
 {% /tab %}
 {% /tabs %}
 
-### 6. Check Batch transaction result
+### 7. Check Batch transaction result
 
 To check the result of the Batch transaction submission:
 
 {% tabs %}
 {% tab label="Javascript" %}
-{% code-snippet file="/_code-samples/batch/js/multiAccountBatch.js" language="js" from="// Check Batch transaction" before="// Verify balances after transaction" /%}
+{% code-snippet file="/_code-samples/batch/js/multiAccountBatch.js" language="js" from="// Check Batch transaction" before="// Calculate and verify" /%}
 {% /tab %}
 {% /tabs %}
 
@@ -136,7 +136,23 @@ The code checks for a `tesSUCCESS` result and displays the response details.
 A `tesSUCCESS` result indicates that the Batch transaction was processed successfully, but does not guarantee the inner transactions succeeded. For example, see the [following transaction on the XRPL Explorer](https://devnet.xrpl.org/transactions/20CFCE5CF75E93E6D1E9C1E42F8E8C8C4CB1786A65BE23D2EA77EAAB65A455C5/simple).
 {% /admonition %}
 
-To verify that the inner transactions have been successful, check the account balances to confirm the expected changes.
+Because the Batch transaction is configured with a `tfAllOrNothing` flag, if any inner transaction fails, **all** inner transactions wil fail, and only the Batch transaction fee is deducted from the **third-party wallet**.
+
+### 8. Verify inner transactions
+
+Since there is no way to check the status of inner transactions, you can verify them by calculating their hashes and looking them up on the ledger:
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/multiAccountBatch.js" language="js" from="// Calculate and verify" before="// Verify balances after transaction" /%}
+{% /tab %}
+{% /tabs %}
+
+The code extracts the actual inner transactions from the batch response, calculates the hash of each inner transaction and looks up each transaction on the ledger using its hash.
+
+### 9. Verify balances
+
+You can also verify that the inner transactions executed successfully by checking the account balances to confirm the expected changes.
 
 {% tabs %}
 {% tab label="Javascript" %}
@@ -144,8 +160,6 @@ To verify that the inner transactions have been successful, check the account ba
 {% /tab %}
 {% /tabs %}
 
-Because the Batch transaction is configured with a `tfAllOrNothing` flag, if any inner transaction fails, **all** inner transactions wil fail, and only the Batch transaction fee is deducted from the **third-party wallet**.
-
 ## See Also
 
 - **Concepts**:

docs/tutorials/how-tos/use-batch-transactions/send-a-single-account-batch-transaction.md

@@ -114,7 +114,7 @@ To check the result of the Batch transaction submission:
 
 {% tabs %}
 {% tab label="Javascript" %}
-{% code-snippet file="/_code-samples/batch/js/singleAccountBatch.js" language="js" from="// Check Batch transaction" before="// Verify balances after transaction" /%}
+{% code-snippet file="/_code-samples/batch/js/singleAccountBatch.js" language="js" from="// Check Batch transaction" before="// Calculate and verify" /%}
 {% /tab %}
 {% /tabs %}
 
@@ -126,7 +126,23 @@ A `tesSUCCESS` result indicates that the Batch transaction was processed success
 For example, see the [following transaction on the XRPL Explorer](https://devnet.xrpl.org/transactions/20CFCE5CF75E93E6D1E9C1E42F8E8C8C4CB1786A65BE23D2EA77EAAB65A455C5/simple).
 {% /admonition %}
 
-To verify that the inner transactions have been successful, check the account balances to confirm the expected changes.
+Because the Batch transaction is configured with a `tfAllOrNothing` flag, if any inner transaction fails, **all** inner transactions wil fail, and only the Batch transaction fee is deducted from the **third-party wallet**.
+
+### 7. Verify inner transactions
+
+Since there is no way to check the status of inner transactions, you can verify them by calculating their hashes and looking them up on the ledger:
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/singleAccountBatch.js" language="js" from="// Calculate and verify" before="// Verify balances after transaction" /%}
+{% /tab %}
+{% /tabs %}
+
+The code extracts the actual inner transactions from the batch response, calculates the hash of each inner transaction and looks up each transaction on the ledger using its hash.
+
+### 8. Verify balances
+
+You can also verify that the inner transactions executed successfully by checking the account balances to confirm the expected changes.
 
 {% tabs %}
 {% tab label="Javascript" %}
@@ -134,8 +150,6 @@ To verify that the inner transactions have been successful, check the account ba
 {% /tab %}
 {% /tabs %}
 
-Because the Batch transaction is configured with a `tfAllOrNothing` flag, if any inner transaction fails, **all** inner transactions wil fail, and only the Batch transaction fee is deducted from the **sender**.
-
 ## See Also
 
 - **Concepts**: