Author

Topic: Bitcoin transaction showing up on blockchain.info but not on blockchain itself (Read 352 times)

copper member
Activity: 2142
Merit: 1305
Limited in number. Limitless in potential.
In this case since the transaction has been rejected and dropped by the network, it seems that the BTC which the sender's sent to your receiving addrrss was returned to the sender's sending address, maybe the reason is low tx fee. You can tell the sender to send it back to you using recommended fees based on this site https://bitcoinfees.21.co
sr. member
Activity: 392
Merit: 268
Tips welcomed: 1CF4GhXX1RhCaGzWztgE1YZZUcSpoqTbsJ
If the original txn is no longer propagating/being stored anywhere (it looks like this is the case) then get 4c23df...2e222c confirmed and send a new transaction.
newbie
Activity: 22
Merit: 0
I believe this is the only unconfirmed input

https://blockchain.info/tx/4c23df09b6d320a9f090e14b704f86cf544d31dee9e8fc8279ccedbae82e222c

As for the tx its not on any other explorer and it never was. It was showing only on blockchain.info (i dont think it got to the mempool)

I am wondering if the tx is still in the system somewhere or he got the btc back and should resend again?
sr. member
Activity: 392
Merit: 268
Tips welcomed: 1CF4GhXX1RhCaGzWztgE1YZZUcSpoqTbsJ
Because the txn is no longer shown on blockchain.info I can't see what inputs/outputs it has, and which of the inputs are acting improperly. If you can provide the raw transaction (or find it on another block explorer) I will be glad to help.
newbie
Activity: 22
Merit: 0
The seller uses blockchain wallet and i am using lbtc as receiving address. I have contacted him and he is happy to help out just need to know what to do.
sr. member
Activity: 392
Merit: 268
Tips welcomed: 1CF4GhXX1RhCaGzWztgE1YZZUcSpoqTbsJ
First, fix the orphaned inputs issue by taking steps to get all of the necessary input transactions to confirm. Then, re-send the existing signed transaction. If you specify what wallet you're using I can try to provide further details.
newbie
Activity: 22
Merit: 0

Thank you very much for your effort

Now i get this

Transaction rejected by our node. Reason: Transaction was previously accepted but has been pruned from our database.

Whats gonna happen now, will the tx get auto resent or?
sr. member
Activity: 392
Merit: 268
Tips welcomed: 1CF4GhXX1RhCaGzWztgE1YZZUcSpoqTbsJ
Edit: This transaction has an orphaned input, ID 4c23df09b6d320a9f090e14b704f86cf544d31dee9e8fc8279ccedbae82e222c, and perhaps other missing inputs. The transactions providing these inputs need to confirm first, after which you can try to push the transaction in question (b9b2f...cd2a) again. This is a potential CPFP situation, depending on how many orphaned inputs there are, and whether all of the unconfirmed input transactions reside in node mempools.


I just tried to push it on a few TX push services, many of which report: "258: txn-mempool-conflict. Code:-26"
Make sure that this transaction isn't a double spend of something that might be found in other nodes' mempools.
newbie
Activity: 22
Merit: 0

Hello guys I could use some help.

I bought some btc today from a guy i ve dealt with a couple of times already.
The transaction shows on blockchain.info where his wallet is but not on other blockchain explorers.

https://blockchain.info/tx/b9b2f9acf8dc37865fb7bb76d58fc9390ceba4cb06e203691ef9f7826114cd2a

I tried to accelerate it via a tool but it says transaction does not exist...

Any feedback is appreciated.

Thanks
Jump to: