439fbc700225418b1a6370981c3bbad0706f75ee83b4596b345b1039794e857e
9b57dabd6a2cfd6c81d881d3f581ce7dc8610089f750267e77258b775ccdd6a6
04823550e67e0076ed6543f1d2431399fc6e728a491b9491510c49f8291cd9c1
I will try all full hours to see, but if someone has an idea I can use it would be great..
There is no way for anybody to be sure wethere or not a certain transaction is sitting in viabtc's mempool... It's possible they rejected a perfectly find transaction while at the same time accepting a transaction whose inputs have been used in a double spending transaction.
That being said, both the first and thirth transaction look ok to me, so there's a big chance viabtc will have them in it's mempool, so there's a big chance you can accellerate them if you submit them at exactly the right moment.
The second transaction uses an unconfirmed parent, chances that this transaction is in viabtc's mempool are a little less than the chances for the first and last transaction.
The only advice i can give you is to keep on trying...
In the following cases, you may be told that your transaction does not exist:
1) Too low fee: We only provide accelerator services for those with at least 0.0001BTC/KB transaction fees;
2) Node reboot: When a Bitcoin node is rebooted, synchronization of transaction data may be delayed. You can try again later;
3) Previous transaction unconfirmed. Your transaction can’t be confirmed if previous transactions connecting to yours are unconfirmed. You’ll need to wait till all previous transactions are confirmed first. You can also use our accelerator to help with that.
We can’t accelerate confirmation of “Double spent” transactions either.