Step 1: getrawtransaction TRANSACTION_ID
- will output RAW_TRANSACTION_HEX
Step 2: sendrawtransaction RAW_TRANSACTION_HEX
- will attempt to "rebroadcast" the transaction to connected peers
Topic: One new block how many transactions it can process? (Read 219 times)
Originally, I didn't send unconfirmed balance. I sent from my balance.
You did.
Your 'balance' does also show unconfirmed balance.
If you do have one 1 BTC output and create a transaction 'sending 0.1 btc', your transaction will basically look like this:
Input:1BTC -> Output1: 0.1BTC, Output2:0.9BTC
After you broadcast this transactions your balance shows 0.9 btc. But this is an unconfirmed balance.
And since you were repeating this step 80 times.. it definitely makes sense that the chain of unconfirmed transactions got too long to be accepted by the majority of nodes.
-> This make senses...
And how to rebroadcast it?
Look here.
Then how about other alt coin's case? How to rebroadcast it? Its same inherited from bitcoin source.
Originally, I didn't send unconfirmed balance. I sent from my balance.
You did.
Your 'balance' does also show unconfirmed balance.
If you do have one 1 BTC output and create a transaction 'sending 0.1 btc', your transaction will basically look like this:
Input:1BTC -> Output1: 0.1BTC, Output2:0.9BTC
After you broadcast this transactions your balance shows 0.9 btc. But this is an unconfirmed balance.
And since you were repeating this step 80 times.. it definitely makes sense that the chain of unconfirmed transactions got too long to be accepted by the majority of nodes.
And how to rebroadcast it?
Look here.
If your transactions are spending unconfirmed transactions, then at some point the chain of unconfirmed transactions will be too long and the transactions won't be accepted by your own node's mempool or other nodes' mempools. This is probably happening resulting in your transactions becoming "stuck" as the other mining node rejects the transactions. You will need to rebroadcast them to that node, and not do them all at once.
Originally, I didn't send unconfirmed balance. I sent from my balance.
And how to rebroadcast it?
And it almost took 1~2 days to confirm, strange thing is, when I sent 50 mil, or 80 mil, it stucked, but when I sent 10 mil, it goes smoothly and fastly.
If your transactions are spending unconfirmed transactions, then at some point the chain of unconfirmed transactions will be too long and the transactions won't be accepted by your own node's mempool or other nodes' mempools. This is probably happening resulting in your transactions becoming "stuck" as the other mining node rejects the transactions. You will need to rebroadcast them to that node, and not do them all at once.
I processed 100 around transactions at once via daemon console, by sendtoaddress command to same address.
I repeatedly typed keyboard fastly with up arrow key and enter key.
From A wallet that has 90 billion coin to B wallet.
50 million at one time sendtoaddress.
After did like 70~80 times, suddenly it says balance is 20, it should be 80 billion.
79 billion is at unconfirmed balance.
Why this happen? Other computer mining this coin, but it can't deal all those 70~80 transactions at one time, but 1~2 transactions at one block.
I see this phenomenon at first time, how describe this situation?
I repeatedly typed keyboard fastly with up arrow key and enter key.
From A wallet that has 90 billion coin to B wallet.
50 million at one time sendtoaddress.
After did like 70~80 times, suddenly it says balance is 20, it should be 80 billion.
79 billion is at unconfirmed balance.
Why this happen? Other computer mining this coin, but it can't deal all those 70~80 transactions at one time, but 1~2 transactions at one block.
I see this phenomenon at first time, how describe this situation?
Jump to: