<p>Your address is in the native-segwit format (also known as bech32).</p>

<p>It's an entirely new address encoding scheme for segwit addresses, and many exchanges, explorers, and wallets don't currently support it. </p>

<p>If you are unable to send coins to it due to the sender not supporting these addresses, you will need to set up a new Electrum wallet, and during the setup process, use P2SH-P2PKH addresses, which will start with <code>M</code>. </p>

<p>If the sender still does not accept the address, you can convert it to one starting with <code>3</code> using <a href="https://litecoin-project.github.io/p2sh-convert/" rel="nofollow noreferrer">https://litecoin-project.github.io/p2sh-convert/</a>.</p>

<p><a href="https://insight.litecore.io" rel="nofollow noreferrer">https://insight.litecore.io</a> will accept addresses starting with <code>M</code> for balance checks, and show outputs to the <code>ltc1</code> addresses, but it will not have an address page for the latter.</p>

CC BY-SA 4.0
2018-10-11T11:24:43.790Z
Thank you for your answer. I don't know if there will be a problem with withdrawal. My withdrawal still has 'confirming' status. We'll see. Thanks!
user2923339
CC BY-SA 4.0
2018-10-11T11:26:25.020Z
@user2923339 If the withdrawal goes through, I wouldn't worry too much about the explorer bit. ltc1 addresses are the future, and the cheapest to send transactions from. You should definitely use them if you can, but may need to fallback to the M/3 addresses if the exchanges/services you use don't support them yet
Raghav Sood
CC BY-SA 4.0
2018-10-11T11:17:15.417Z
2018-10-11T11:39:23.447Z
2018-10-11T11:39:23.447Z
Raghav Sood
<p>my litecoin wallet (shared 2 of 2) on electrum-ltc generated an address to receive LTC. I transfered some LTC to that address and tried to check in block explorer. Unfortunately got such message:
Sorry, 'ltc1qy4rwhdkujk35ga26774gqmng67kgggtqnsx9vp0xgzp3wz3yjkhqashszw' is not a valid LTC address, wallet name, transaction or block.</p>

<p>Is it something wrong with my LTC address? Electrum-ltc v 3.1.3.1. From what I know it is Bech32 Segwit address.</p>

<address><electrum><bech32-address>
Litecoin address starting with ltc
user2923339
# Litecoin address starting with ltc

(Asked by: username_0 on 2018-10-11)

my litecoin wallet (shared 2 of 2) on electrum-ltc generated an address to receive LTC. I transfered some LTC to that address and tried to check in block explorer. Unfortunately got such message:
Sorry, 'ltc1qy4rwhdkujk35ga26774gqmng67kgggtqnsx9vp0xgzp3wz3yjkhqashszw' is not a valid LTC address, wallet name, transaction or block.

Is it something wrong with my LTC address? Electrum-ltc v 3.1.3.1. From what I know it is Bech32 Segwit address.

**Tags:** address, electrum, bech32-address


---

## 1 answers

### Answer by username_1 on 2018-10-11. Score: 4 | Accepted answer

Your address is in the native-segwit format (also known as bech32).

It's an entirely new address encoding scheme for segwit addresses, and many exchanges, explorers, and wallets don't currently support it.

If you are unable to send coins to it due to the sender not supporting these addresses, you will need to set up a new Electrum wallet, and during the setup process, use P2SH-P2PKH addresses, which will start with `M`.

If the sender still does not accept the address, you can convert it to one starting with `3` using <https://litecoin-project.github.io/p2sh-convert/>.

<https://insight.litecore.io> will accept addresses starting with `M` for balance checks, and show outputs to the `ltc1` addresses, but it will not have an address page for the latter.

> **Comments:**
> **username_0**: Thank you for your answer. I don't know if there will be a problem with withdrawal. My withdrawal still has 'confirming' status. We'll see. Thanks!  
> **username_1**: @username_0 If the withdrawal goes through, I wouldn't worry too much about the explorer bit. ltc1 addresses are the future, and the cheapest to send transactions from. You should definitely use them if you can, but may need to fallback to the M/3 addresses if the exchanges/services you use don't support them yet  

---

