The fee is too low. Who recommended you that fee? Blockchain.info? If so, that is your problem. Blockchain.info's wallet has absolutely horrendous fee estimation, among several other issues.

Your transaction only pays a fee of 129 sat/byte, which is way lower than the 390 sat/byte recommended by https://bitcoinfees.21.co/.

Please read https://bitcointalk.org/index.php?topic=1802212.0

Firstly, if your only concern about Core is that it is using too much disk space, you can enable pruning. Go to the Bitcoin Core datadir and find or create the bitcoin.conf file (it's just a text file with a .conf extension). Then add the following line to it:

That will reduce the size of the blockchain to ~1-2 GB. What it does is it will just delete the blockchain except for the most recent 288 or so blocks. As you get more blocks, the oldest blocks will be deleted to make space for the new ones.

If you really want to go ahead with transferring the Bitcoin to a new wallet, you will need to do a few things to get abandontransaction to work. First, stop Bitcoin Core. Then go to the Bitcoin Core datadir and delete the file called mempool.dat if it exists. Then start Bitcoin Core with the -walletbroadcast=0 option. Then you should be able to do Abandon Transaction.

AFAIK, you can't have Mycelium "forget" about your transactions.

You can't force anyone else on the network (like miners and nodes) to forget about your transaction.

All you can do is wait for everyone to forget the transaction or for it to confirm.

Yes. You don't even need to change anything in the datadir (like swapping in the wallet.dat file) since the latest version of Core will just use what is already there.

How are you requesting the block? Can you show us the code?

This topic has been moved to Trashcan.

Removed upon request

Try starting Bitcoin Core manually. First start Armory. Then uncheck the "Let Armory run Bitcoin Core in the background" box in File > Settings. Then stop Armory. Start Bitcoin Core and let it sync and get fully started. Then start Armory. It should then say that you are online. Then you can send. If you are not online, you will not be able to send transactions.

A lightweight wallet connects to a full node and asks from that node for information related to itself. It essentially gives that node a list of its addresses and asks that the full node only relay transactions which pertain to those addresses. The private keys themselves are still stored within the wallet and are not exposed to the full nodes that it connects to. In exchange for the convenience of not having the entire blockchain, you lose some privacy and security as you have to trust that the full node is providing the correct data.

It's likely that there originally were transactions to your wallet but they were unconfirmed and were eventually dropped by the network. Your wallet still remembers them though which is why it displays them to you. The question mark next to them indicates that the wallet is confused about those transactions since they are there locally but not in the blockchain.

No. If you forgot your password, then you can't do anything with the wallet.

Click the Receive Bitcoin button and you will get an address you can use. Your wallet does not just have one address, you will get a new address every time you click Receive Bitcoin.

Get a Bitcoin address from alphabay and then send to that address. There is nothing in Bitcoin for "deposit at service X". No decent wallet is going to have any such specific option.

If the transactions are not particularly important, then pretty much.

Transaction 1 spends from the confirmed transaction. The way that Bitcoin works is that outputs must be spent completely, so transaction 1 spends your output from the confirmed transaction and produces a change output which is what transaction 2 spends from.

It should be "returned" in a few days. However this does not mean that it will disappear from your wallet.

This transaction has confirmed.

This transaction is unconfirmed. Lets call it transaction #1. It pays an extremely low transaction fee, only 6 sat/byte whereas the recommended transaction fee is 360 sat/byte.

This transaction is also unconfirmed. Lets call it transaction #2. It pays a fairly low transaction fee, only 166 sat/byte. However, it also spends from transaction #1, so it cannot confirm until transaction #1 confirms too.

This transaction is also unconfirmed. Lets call it transaction #3. It pays a low fee, only 222 sat/byte. However, it also spends from transaction #2 so it cannot confirm until transaction #2 confirms too.

If you are using an old version of Multibit, it is very likely that your transactions paid an insufficient transaction fee. Since you also sent transactions from an unconfirmed transaction, those other transactions cannot confirm until the first one confirms as well.

Please post the txids of the transactions so that we can see what is actually wrong.

Your first transaction has confirmed.

Your second transaction spends from this unconfirmed transaction: https://blockchain.info/tx/72b2bf6117119e10b50b57a412e68111c8bdd5bc6651e68e694862ec1b7d37b1. That transaction spends from this other unconfirmed transaction: https://blockchain.info/tx/2e8b79e9e7d8035da432c4847983b61874bab334ecd6a2fd5c4ecc72ee3ad980. Your transaction cannot confirm until both of these confirm too.

You have inbound connections, your node is reachable. Bitnodes is not guaranteed to always work. If their crawler is unable to reach you, that does not necessarily mean that you are not reachable. Curl won't work since the node will not send you any data unless you first send the version message.