Actions77
- Address History Actions
- Address Latest Actions
- AML Actions
- Block Data Actions
- Blockchain Event Actions
- Blockchain Fee Actions
- Estimate Contract Interaction Gas
- Estimate FA1.2 Transfer Fee
- Estimate FA2 Transfer Fee
- Estimate Native Coin Transfer Compute Units
- Estimate Native Coin Transfer Gas
- Estimate Program Invocation Compute Units
- Estimate Token Transfer Compute Units
- Estimate Token Transfer Gas
- Estimate Transaction Smart Fee
- Estimate Transfer Fee
- Get EIP-1559 Fee Recommendations
- Get Fee Recommendations
- Broadcast Actions
- Contract Actions
- HD Wallet Actions
- Market Data Actions
- Prepare Transaction Actions
- Simulate Actions
- Transaction Data Actions
- Utility Actions
HD Wallet → Prepare Transaction
AI-generatedSummary
Prepares a transaction for an HD wallet using its extended public key and the selected blockchain, network, and fee priority. For EVM, provide a recipient and native coin amount, with optional calldata; for UTXO, provide recipients as an array of address and amount pairs.
Inputs
- Blockchain Type — Select Management, EVM, UTXO, or XRP. Defaults to Management in the UI; the implementation defaults to EVM if the selector is absent.
- Blockchain (required) — Choose a supported chain for the selected blockchain type. Management offers Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash, Ethereum, Ethereum Classic, Binance Smart Chain, Tron, and XRP; EVM offers Ethereum, Ethereum Classic, Binance Smart Chain, and Tron; UTXO offers Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash. XRP uses its blockchain type directly.
- Network (required) — Choose the network for the selected chain. Available networks depend on the chain; unsupported blockchain and network pairs are rejected by the API.
- Extended Public Key (required) — HD wallet xPub, yPub, or zPub used to prepare the transaction.
- To Address (required) — For EVM transactions, enter the recipient address.
- Value (required) — For EVM transactions, enter the amount in the native coin's smallest unit, such as wei.
- Calldata — Optional hex-encoded calldata for EVM contract interactions.
- Recipients (JSON) (required) — For UTXO transactions, provide an array of recipient objects with address and amount fields.
- Fee Priority — Select Standard, Slow, or Fast; defaults to Standard.
Output shape
A single item containing the prepared transaction data returned by the Crypto APIs response.
The node unwraps the API's data.item response. XRP is available as a blockchain type, but this operation's UI properties do not declare transaction-specific fields for it.
Examples
Example 1: Build a native EVM transfer
Select EVM, choose a supported chain and network, then enter the extended public key, recipient address, native coin amount in its smallest unit, and optionally calldata and fee priority.
Example 2: Build a UTXO transaction with multiple outputs
Select UTXO, choose a supported chain and network, enter the extended public key, and provide recipients as JSON objects containing address and amount.