Skip to main content

Sending a Manually Built Transaction in the Browser

After constructing and signing your transaction manually, the next step is broadcasting it to the network. This guide explains how to send these transactions in a browser environment.

Important Note

If you use the method described for manually building a transaction with OP_WALLET (see Building a Transaction Manually), you can simplify the process by using opnet.web3.signAndBroadcastInteraction(). This method combines signing and broadcasting into a single step, eliminating the need for manual transaction broadcasting.

Sending Raw Transactions in the Browser​

To send manually built and signed transactions, you can use the provider.sendRawTransaction method. Each signed transaction must be sent sequentially.

// Send the first transaction
const firstTx = await provider.sendRawTransaction(signedTransaction[0], false);

if (!firstTx || !firstTx.success) {
  throw new Error("First transaction failed");
}

// Send the second transaction
const secondTx = await provider.sendRawTransaction(signedTransaction[1], false);

if (!secondTx || !secondTx.success) {
  throw new Error("Second transaction failed");
}

console.log("Transaction hash:", secondTx.result);

Best Practices​

  • Simplify your workflow by using this method instead of manually handling transactions.
  • If sending transactions manually, ensure they are executed in the correct sequence.
  • Record transaction hashes for auditing and debugging purposes.
Last updated on