The absolute fee of the original transaction in satoshis. This is used as the basis for fee calculations and comparisons.
The type of Bitcoin address used (e.g., P2PKH, P2SH, P2WPKH, P2WSH). This is used to determine the input size for different address types when estimating transaction size.
An array of Unspent Transaction Outputs (UTXOs) that are available for fee bumping. These are potential inputs that can be added to a replacement transaction in RBF, or used to create a child transaction in CPFP.
OptionalchangeThe index of the change output in the transaction, if known. This helps identify which output is the change and can be adjusted for fee bumping in RBF scenarios.
OptionalincrementalThe incremental relay fee-rate in satoshis per vbyte. This is the minimum fee rate increase required for nodes to accept a replacement transaction. It's used in RBF calculations to ensure the new transaction meets network requirements. Default value in Bitcoin Core is 1 sat/vbyte.
The Bitcoin network to use (mainnet, testnet, or regtest).
The number of signatures required in a multisig setup. This is used to estimate transaction size more accurately for multisig transactions.
The target fee rate in satoshis per vbyte that the user wants to achieve. This is used to determine if fee bumping is necessary and to calculate the new fee for RBF or CPFP.
The total number of signers in a multisig setup. This is used along with requiredSigners to estimate transaction size more accurately for multisig transactions.
The hexadecimal representation of the raw transaction. This is used for parsing the transaction details directly from the hex .
Configuration options for the TransactionAnalyzer.
Remarks
TXID Format Convention: All transaction hex data and TXID references provided to this analyzer should use big-endian format (human-readable format).