Title: How block explorers work(Unconfirmed transaction) Post by: Dr.Z on December 04, 2017, 06:16:19 AM I know each node has its own mempool for transactions to be mined. My question is, for those unconfirmed transactions shown in the block explorers, are they in the explorer's own mempool, or they can also be transactions from other nodes' mempool?
If one transaction has been on Chain.so for 24 hours but not on other explorers, does it means that this transaction is created by Chain.so, and Chain.so has not broadcast this transaction into the network? Title: Re: How block explorers work(Unconfirmed transaction) Post by: ranochigo on December 04, 2017, 06:47:16 AM My question is, for those unconfirmed transactions shown in the block explorers, are they in the explorer's own mempool, or they can also be transactions from other nodes' mempool? Would have to be the transaction from the block explorer's own mempool.If one transaction has been on Chain.so for 24 hours but not on other explorers, does it means that this transaction is created by Chain.so, and Chain.so has not broadcast this transaction into the network? No. Each nodes have their own set of rules to accept transactions. They can select which set of rules they want to follow or which they don't. For most nodes, they differ in the minimum relay fee. Which is the fee/kb requirement to accept transactions into the pool. Either the transaction's fees are too low or the transaction isn't well propagated. Title: Re: How block explorers work(Unconfirmed transaction) Post by: Dr.Z on December 04, 2017, 07:28:13 AM My question is, for those unconfirmed transactions shown in the block explorers, are they in the explorer's own mempool, or they can also be transactions from other nodes' mempool? Would have to be the transaction from the block explorer's own mempool.If one transaction has been on Chain.so for 24 hours but not on other explorers, does it means that this transaction is created by Chain.so, and Chain.so has not broadcast this transaction into the network? No. Each nodes have their own set of rules to accept transactions. They can select which set of rules they want to follow or which they don't. For most nodes, they differ in the minimum relay fee. Which is the fee/kb requirement to accept transactions into the pool. Either the transaction's fees are too low or the transaction isn't well propagated. I know the fee is too low. But Chain.so shows the transaction, does this mean that this transaction is in Chain.so's mempool? Also, do all nodes have a mempool? or just miners? If the fee is too low that other nodes won't accept this transaction, only Chain.so has it in the mempool, does it mean that I have to wait until Chain.so successfully mines a block? Thank you! Title: Re: How block explorers work(Unconfirmed transaction) Post by: achow101 on December 04, 2017, 08:02:25 AM I know the fee is too low. But Chain.so shows the transaction, does this mean that this transaction is in Chain.so's mempool? Yes.Also, do all nodes have a mempool? or just miners? Most full nodes have a mempool. However you can also configure one to not have one and operate in blocks only mode.If the fee is too low that other nodes won't accept this transaction, only Chain.so has it in the mempool, does it mean that I have to wait until Chain.so successfully mines a block? Chain.so is not a miner. If your transaction is not in anyone else's mempool (and determining this is impossible to do), then your transaction will not be mined. You can remedy that by rebroadcasting the transaction to the network so that it does enter all nodes' mempools, but it may drop out of them again later, so you would have to rebroadcast again later.Title: Re: How block explorers work(Unconfirmed transaction) Post by: Dr.Z on December 04, 2017, 08:49:54 AM Chain.so is not a miner. If your transaction is not in anyone else's mempool (and determining this is impossible to do), then your transaction will not be mined. You can remedy that by rebroadcasting the transaction to the network so that it does enter all nodes' mempools, but it may drop out of them again later, so you would have to rebroadcast again later. Thank you. What happened to me was, the transaction(5225cff0ac48fa59ff85553cb515e21560abbcdd0711f1179f8cd189a792d121) had been on Chain.so for 48hours while no other block explorers were showing it. However, a day later, that transaction finally went through. Any thoughts on what was happened?Now I have another one in the same situation. No one is showing it except Chain.so 0a031d2e72904b7d90cc6de55f913b489be2613f9b5acd43a5cd5158d1cf7c76 Title: Re: How block explorers work(Unconfirmed transaction) Post by: ranochigo on December 04, 2017, 09:17:31 AM Thank you. What happened to me was, the transaction(5225cff0ac48fa59ff85553cb515e21560abbcdd0711f1179f8cd189a792d121) had been on Chain.so for 48hours while no other block explorers were showing it. However, a day later, that transaction finally went through. Any thoughts on what was happened? Chain.so's mempool is not reflective of every mempool in the network. This means that even if only chain.so has the transaction on their block explorer, it doesn't mean that the miners doesn't have it on their mempool. Now I have another one in the same situation. No one is showing it except Chain.so 0a031d2e72904b7d90cc6de55f913b489be2613f9b5acd43a5cd5158d1cf7c76 What client did you use to send the transaction? Title: Re: How block explorers work(Unconfirmed transaction) Post by: Dr.Z on December 04, 2017, 11:50:05 AM [quote ]
Chain.so's mempool is not reflective of every mempool in the network. This means that even if only chain.so has the transaction on their block explorer, it doesn't mean that the miners doesn't have it on their mempool. [/quote] I think if most of the block explores not showing it, then miners dont have it on their mempool.? Title: Re: How block explorers work(Unconfirmed transaction) Post by: ranochigo on December 04, 2017, 12:01:31 PM I think if most of the block explores not showing it, then miners dont have it on their mempool.? Definitely highly probable. Which client are you using as a wallet? If you are using a desktop wallet, you would most likely be able to get the raw transaction and broadcast it yourself.Title: Re: How block explorers work(Unconfirmed transaction) Post by: Dr.Z on December 05, 2017, 01:10:10 AM Definitely highly probable. Which client are you using as a wallet? If you are using a desktop wallet, you would most likely be able to get the raw transaction and broadcast it yourself. Those transactions are payouts I got from a cloud mining service. Maybe they create transactions using Chain.so and pay low fees, the transactions were in Chain.so'queue and not even in the mempool(and maybe Chain.so's explorer shows transactions in the queue as well). And after days it finally got broadcasted into the network.Title: Re: How block explorers work(Unconfirmed transaction) Post by: DannyHamilton on December 05, 2017, 06:12:50 PM I think if most of the block explores not showing it, then miners dont have it on their mempool.? Block explorers do not get to choose what a miner will or will not include in his mempool or his blocks. Block explorers just tell you about the transactions that they choose to out of the transactions that they have heard about. This is in no way an indication of what any other node or miner has heard about or chosen to accept. |