pull down to refresh

0 sats \ 11 replies \ @bitcoingraffiti OP 15h \ parent \ on: Quick tx fee rate settings bitdevs
The weird thing though is that I can't find those utxos on a blockchain explorer.
write
preview
0 sats \ 10 replies \ @optimism 15h
hmm how far away are you from sync?
reply
100 sats \ 9 replies \ @bitcoingraffiti OP 15h
839168; apr 2024
reply
21 sats \ 8 replies \ @optimism 15h
So with 27.x you're beyond assumevalid - this is where your node checks every tx script, which is why it's a bit slower now... may take a day or 2 if yesterday around this time you were at 2023.
I'd just go to https://mempool.space/tx/push (with appropriate vpn or whatever you use for safety) and push the tx there.
reply
100 sats \ 7 replies \ @bitcoingraffiti OP 14h
Ok, but how is it that I can't find my utxo's back on a blockchain explorer?
reply
0 sats \ 6 replies \ @optimism 14h
you're querying for the inputs of your last tx?
reply
0 sats \ 5 replies \ @bitcoingraffiti OP 14h
No, i checked the txids of what was in listunspent 0
reply
21 sats \ 4 replies \ @optimism 14h
I think that that is what you couldn't send out yet? So you'll want to query for the inputs of these. run the hex through bitcoin-tx -json <hex>, take the inputs there, these should exist.
reply
100 sats \ 3 replies \ @bitcoingraffiti OP 13h
Ok. Yeah, they do exist.
Ok, so I could now create a new rawtransaction hex and then push it on the network, right?
view all 3 replies