úÎ/Ñ,°     None24tThe OutPoint is used inside a transaction input to reference the previous transaction output that it is spending. (The hash of the referenced transaction. \The position of the specific output in the transaction. The first output position is 0. JSON of "multisig" received. JSON of "scripthash" received. JSON of "pubkeyhash" received. JSON of "pubkey" received. ,Data type representing a transaction input. <Reference the previous transaction output (hash + position) _Script providing the requirements of the previous transaction output to spend those coins. ¼Transaction version as defined by the sender of the transaction. The intended use is for replacing transactions with new information before the transaction is included in a block. -Data type representing a transaction output. Transaction output value. 7Script specifying the conditions to spend this output. -Data type representing a bitcoin transaction  Transaction data format version List of transaction inputs List of transaction outputs BThe block number of timestamp at which this transaction is locked 5Data type representing the coinbase transaction of a Blockÿ-. Coinbase transactions are special types of transactions which are created by miners when they find a new block. Coinbase transactions have no inputs. They have outputs sending the newly generated bitcoins together with all the block's fees to a bitcoin address (usually the miners address). Data can be embedded in a Coinbase transaction which can be chosen by the miner of a block. This data also typically contains some randomness which is used, together with the nonce, to find a partial hash collision on the block's hash. !Transaction data format version. sPrevious outpoint. This is ignored for coinbase transactions but preserved for computing the correct txid. /Data embedded inside the coinbase transaction. }Transaction sequence number. This is ignored for coinbase transactions but preserved for computing the correct txid. List of transaction outputs. GThe block number of timestamp at which this transaction is locked. 9 !"#$%&'()*+ ,-./0123456789:;3 !"#%&()* ,-/012356789: !"#$%&'()*+  ,-./0123456789:;None5Decodes a hex representation of a transaction into a   object.  Encodes a  # object into a hex representation. #Calculates the transaction id of a   as a <* so it can be used in RPC interfaces. 2The hexadecimal representation of the transaction  The decoded   object The   we would like to encode to hex 2The hexadecimal representation of the transaction   =        !"#$%&'()*+,-./0123456789:;<bitcoin-tx-0.13.0Data.Bitcoin.TransactionData.Bitcoin.Transaction.Types TransactionIn _prevOutput _scriptInput _txInSequenceTransactionOut _outValue _scriptOutput Transaction _txVersion_txIn_txOut _txLockTimeCoinbasedecodeencode transactionIdOutPoint _outPointHash_outPointIndex TxnMultisig TxnScriptHash TxnPubKeyHash TxnPubKey _cbVersion _cbPrevOutput_cbData _cbInSequence_cbOut _cbLockTimeTransactionHash TxnOutputType$fBinaryTransactionHash outPointHash outPointIndex$fBinaryOutPoint prevOutput scriptInput txInSequence$fBinaryTransactionInoutValue scriptOutput$fBinaryTransactionOuttxIn txLockTimetxOut txVersion$fBinaryTransactioncbData cbInSequence cbLockTimecbOut cbPrevOutput cbVersion$fBinaryCoinbasebitcoin-types-0.9.2Data.Bitcoin.Types TransactionId