Skip to main content

Parameters

string
required
Fully-signed transaction as a base-64 encoded string
object
Configuration object containing:
string
Encoding format for the transaction (base58, base64, json)
string
Commitment level (processed, confirmed, finalized)
string
Commitment level for preflight (processed, confirmed, finalized)
boolean
If true, skip the preflight transaction checks
number
Maximum number of times for the RPC node to retry sending the transaction to the leader
number
The minimum slot that the request can be evaluated at

Response

string
First transaction signature embedded in the transaction (base-58 encoded)

Code Examples

Basic Request

Using web3.js

Notes

  1. Submits a signed transaction to the cluster
  2. The transaction must be fully signed
  3. The response is the transaction signature
  4. The transaction must be confirmed before changes are applied
  5. The transaction must include a recent blockhash

Best Practices

  1. Use appropriate commitment level based on your needs
  2. Wait for transaction confirmation before proceeding
  3. Handle rate limits and network errors
  4. Monitor transaction status for failures
  5. Consider using preflight checks for validation

Common Errors

Use Cases

  1. Transaction Management
  2. Transaction Monitoring
  3. Transaction Planning