You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Additionally, if include_removed is set, transactions affecting the wallet which were removed are returned in the \"removed\" array.\n"
1762
1762
"\nArguments:\n"
1763
1763
"1. \"blockhash\" (string, optional) The block hash to list transactions since\n"
1764
-
"2. target_confirmations: (numeric, optional, default=1) The confirmations required, must be 1 or more\n"
1764
+
"2. target_confirmations: (numeric, optional, default=1) Return the nth block hash from the main chain. e.g. 1 would mean the best block hash. Note: this is not used as a filter, but only affects [lastblock] in the return value\n"
1765
1765
"3. include_watchonly: (bool, optional, default=false) Include transactions to watch-only addresses (see 'importaddress')\n"
1766
1766
"4. include_removed: (bool, optional, default=true) Show transactions that were removed due to a reorg in the \"removed\" array\n"
" <structure is the same as \"transactions\" above, only present if include_removed=true>\n"
1795
1795
" Note: transactions that were readded in the active chain will appear as-is in this array, and may thus have a positive confirmation count.\n"
1796
1796
" ],\n"
1797
-
"\"lastblock\": \"lastblockhash\" (string) The hash of the last block\n"
1797
+
"\"lastblock\": \"lastblockhash\" (string) The hash of the block (target_confirmations-1) from the best block on the main chain. This is typically used to feed back into listsinceblock the next time you call it. So you would generally use a target_confirmations of say 6, so you will be continually re-notified of transactions until they've reached 6 confirmations plus any new ones\n"
0 commit comments