I copied transaction id of a random transaction from block explorer: c04878631aa447edf47087aa9583a0e1113f6e4bba12d33f3610ce0242c72855
Run below command in Bitcoin Core:
getrawtransaction c04878631aa447edf47087aa9583a0e1113f6e4bba12d33f3610ce0242c72855 true
It returns below information for this transaction:
There is no way for a block explorer to know which addresses belong to the same wallets, in fact no block explorer shows the balance of wallets but only by addresses.
The only way to know which addresses are from the same wallet is having generated that wallet or having it's seed.
Wallets are a client structure that collects all the addresses for which you ...
Big disclaimer: you really shouldn't do this. Transaction prioritization works based on fee per size, so that's what you should be configuring.
As for an explanation of what you're seeing: the block explorer you're using is showing the wrong size. For fee computations what you need is the vsize, not the serialized size. This is the size that takes the ...
"txs" : n, (numeric) The number of transactions (including coinbase)
C:\Program Files\Bitcoin\daemon> bitcoin-cli getblockcount
C:\Program Files\Bitcoin\daemon> bitcoin-cli getblockstats 627251 | findstr /C:"\"txs\":"
The full output contains ...
If you are trying to load a wallet, then you do not need to be using a wallet specific endpoint. loadwallet is not actually a wallet RPC so it does not need the wallet specific endpoint.
If you are trying to access a wallet that has already been loaded, then you have the wrong endpoint. The endpoint does not include the wallet.dat file. Bitcoin Core gives ...
regtest is the test network best suited for this kind of testing. While it does still have a PoW requirement, the work required is basically negligible. It also does not do retargeting so the difficulty does not change. This allows you to create blocks at will. So you can use the regtest network option in order to test that your code is creating blocks ...
Tons of red flags here.
I've been around for a while and have never heard of this client.
Browsing the site, all the pages dedicated to code or developer documentation are non-existent or lead to placeholders.
I reached out to Will Binns whose name is given as the maintainer of
the ostensible "Bitcoin client" Bitly Core on the "developer
Seems that you have an error in bitcoind starting options, you have -daemonwait instead of -daemon, you can check with systemctl cat bitcoind.service
The file to edit should be /etc/systemd/system/bitcoind.service
The issue here is that the two transactions are different, and combinerawtransaction does not operate on different transactions (it apparently just silently does nothing). It sounds like you expect combinerawtransaction to take two separate transactions and create a new one which has the inputs and outputs of both transactions. (or perhaps take two ...
Since i still have unspent amount in that transactionId so i used the same TransactionId this time as well.
This is incorrect. You cannot use the same transaction ID. You have to use the new transaction ID to spend new UTXO. The input was also used as change address in the transaction so you have a new UTXO associated with the same address. I will share one ...