The time the transaction entered the memory pool, Unix epoch time format
→ → height
number (int)
Required (exactly 1)
The block height when the transaction entered the memory pool
→ → startingpriority
number (int)
Required (exactly 1)
The priority of the transaction when it first entered the memory pool
→ → currentpriority
number (int)
Required (exactly 1)
The current priority of the transaction
→ → descendantcount
number (int)
Required (exactly 1)
Added in Bitcoin Core 0.12.0
The number of in-mempool descendant transactions (including this one)
→ → descendantsize
number (int)
Required (exactly 1)
Added in Bitcoin Core 0.12.0
The size of in-mempool descendants (including this one)
→ → descendantfees
number (int)
Required (exactly 1)
Added in Bitcoin Core 0.12.0
The modified fees (see modifiedfee above) of in-mempool descendants (including this one)
→ → depends
array
Required (exactly 1)
An array holding TXIDs of unconfirmed transactions this transaction depends upon (parent transactions). Those transactions must be part of a block before this transaction can be added to a block, although all transactions may be included in the same block. The array may be empty
GetRawMemPoolRPC: returns all transaction identifiers (TXIDs) in the memory pool as a JSON array, or detailed information about each transaction in the memory pool as a JSON object.
The GET tx operation gets a hex-encoded serialized transaction or a JSON object describing the transaction. By default, Dash Core only stores complete transaction data for UTXOs and your own transactions, so this method may fail on historic transactions unless you use the non-default txindex=1 in your Dash Core startup settings.
Note: if you begin using txindex=1 after downloading the block chain, you must rebuild your indexes by starting Dash Core with the option -reindex. This may take several hours to complete, during which time your node will not process new blocks or transactions. This reindex only needs to be done once.
Request
Parameter #1—the TXID of the transaction to retrieve
An array of objects with each object being an input vector (vin) for this transaction. Input objects will have the same order within the array as they have in the transaction, so the first input listed will be input 0
The number of duffs paid to this output. May be 0.
Only present if spentindex enabled
→ → → → addresses
string : array
Optional (0 or 1)
The P2PKH or P2SH addresses used in this transaction, or the computed P2PKH address of any pubkeys in this transaction. This array will not be returned for nulldata or nonstandard script types.
An array of objects each describing an output vector (vout) for this transaction. Output objects will have the same order within the array as they have in the transaction, so the first output listed will be output 0
The number of signatures required; this is always 1 for P2PK, P2PKH, and P2SH (including P2SH multisig because the redeem script is not available in the pubkey script). It may be greater than 1 for bare multisig. This value will not be returned for nulldata or nonstandard script types (see the type key below)
→ → → → type
string
Optional (0 or 1)
The type of script. This will be one of the following: · pubkey for a P2PK script · pubkeyhash for a P2PKH script · scripthash for a P2SH script · multisig for a bare multisig script · nulldata for nulldata scripts · nonstandard for unknown scripts
→ → → → addresses
string : array
Optional (0 or 1)
The P2PKH or P2SH addresses used in this transaction, or the computed P2PKH address of any pubkeys in this transaction. This array will not be returned for nulldata or nonstandard script types
GetRawTransactionRPC: gets a hex-encoded serialized transaction or a JSON object describing the transaction. By default, Dash Core only stores complete transaction data for UTXOs and your own transactions, so the RPC may fail on historic transactions unless you use the non-default txindex=1 in your Dash Core startup settings.