broadcast_tx_commit request type
Use a freshly signed base64 transaction for each request. This legacy synchronous send is still documented, but send_tx is the preferred path for new integrations, and the sample payload is illustrative only.
Broadcast a base64-encoded `SignedTransaction`; blocks until execution completes or a 10-second timeout elapses. Deprecated — use `send_tx`. Example payloads are placeholders and cannot be replayed.
Responses from the selected endpoint appear here after you run a request.
Live response output will appear here after you run a request.
This operation accepts a JSON-RPC body over POST to /.
Required request inputs: yes
{
"jsonrpc": "2.0",
"id": "fastnear",
"method": "broadcast_tx_commit",
"params": {
"signed_tx_base64": "CQAAAG1pa2UubmVhcgD64cHVt7yB8HSzql1e8RLKSv2riwv7+vNviWHD/y95EgEAAAAAAAAADQAAAG1pa2V0ZXN0Lm5lYXJBM1Y72BJnk/V7dlrTRBxxxUxyB/JXo+hODCyF0woAEAEAAAADAQAAAAAAAAAAAAAAAAAAAADiGG3IJC5QsOBN70h+glB+U9nBYEXObdaPHMjXyu2YQbQUvALIWbdBBxhuR9VQ/fEXg7L0vGSCd9wCCrq0CFIF"
}
}jsonrpc *string2.0id *stringmethod *stringbroadcast_tx_commitparams *objectsigned_tx_base64 *stringBase64-encoded signed transaction
wait_untilstringDesired level of execution status guarantee
NONEINCLUDEDINCLUDED_FINALEXECUTEDEXECUTED_OPTIMISTICFINALSuccessful response
jsonrpc *string2.0id *one ofresultobjectfinal_execution_status *stringDesired level of execution status guarantee
NONEINCLUDEDINCLUDED_FINALEXECUTEDEXECUTED_OPTIMISTICFINALreceiptsarrayReceipts generated from the transaction
itemsobjectreceipts_outcomearrayThe execution outcome of receipts.
itemsobjectstatusobjectOne of multiple possible types
transactionobjectSigned Transaction
transaction_outcomeobjectThe execution outcome of the signed transaction.
errorobjectcodeintegermessagestringdataobject