Solana · Arazzo Workflow
Solana Submit a Transaction and Confirm It
Version 1.0.0
Fetch a blockhash, simulate a signed transaction, send it, poll to finality, and read it back.
Provider
Workflows
send-transaction-lifecycle
Simulate, submit, and confirm a signed Solana transaction end to end.
Takes a signed, encoded transaction and carries it through the full submit lifecycle, aborting before submission if the simulation reports an error.
1
fetchBlockhash
getLatestBlockhash
Fetch a recent blockhash and the last block height at which it stays valid. The client signs the transaction against this blockhash, and the expiry height bounds how long confirmation polling is worth attempting.
2
simulate
simulateTransaction
Dry-run the signed transaction against the current bank without broadcasting it. Signature verification is enabled, and the step only succeeds when the simulated result carries no error, so a transaction that would fail on-chain is never submitted.
3
submit
sendTransaction
Relay the signed transaction to the cluster as-is. The node returns the base58 transaction signature, which is the handle used to track confirmation.
4
confirm
getSignatureStatuses
Poll the signature status until the cluster reports it finalized. The step retries on a short interval because a freshly submitted transaction takes several slots to reach finality.
5
fetchTransaction
getTransaction
Read the finalized transaction back in parsed form to capture the slot it landed in, the fee actually charged, and the on-chain log messages.