Transaction not found on BC Blockexplorer*Solved Thx*

[bbbydistheword]

Electrum 2.0.4

Tried to send a couple times but it gave me some "network doesn't support transactions" error. So I switched the network to some random one (h.1209k.com)
Now it went thru and says "pending" . . . but when I check blockchain "Transaction not found"  is this common? Whats up? It's been like 10 hours no change

***Thanks to all who helped me. I downloaded the new version and it went through

[1715263201]

1715263201

[1715263201]

1715263201

[twister]

Electrum 2.0.4

Tried to send a couple times but it gave me some "network doesn't support transactions" error. So I switched the network to some random one (h.1209k.com)
Now it went thru and says "pending" . . . but when I check blockchain "Transaction not found"  is this common? Whats up? It's been like 10 hours no change

Could you provide the Tx ID from the electrum.

I think it's because you're using an older version of Electrum. You need to update to the latest version. Download the latest version and restore your wallet in it, it will show the right balance of your address and then you can re-send the transaction, make sure to add extra fee because there is a Dos attack going on.

[medUSA]

Electrum 2.0.4

You are using an old version of electrum. Update to the latest version and everything should be fine. Pre version 2.5 uses "high-s" signatures to sign transactions and now they are considered "non-standard".

[ranochigo]

It is not good for blockexplorer to be not seeing your transaction. Your fee might be too low or your client did not broadcast your transaction at all. Right click the problematic transaction and press save. Next, open the .txn file and copy the hex without the " ". Go to coinb.in/#broadcast and enter the hex code there and send. You should see a green box with your TXID or an error. If there's an error, post it here.
Edit: I totally forgot about the BIP62 sorry.

BIP62 was implemented in Electrum 2.5. It could be a problem since Bitcoin nodes are not relaying transactions with high S value in the signature. Upgrading the client will solve the problem.