As others already have mentioned, this is the 'new' segwit format (bech32). This is the 'true' segwit format.
Nested segwit (P2PKH nested into P2SH; address starting with 3..) is 'kind of segwit'. To be more precise, it is legacy data fetched into segwit format.
I guess you might be irritated and refering to it as camouflaged because you can't click on the address ?
If so, this has nothing to do with the address format itself, but with blockchain.com. They simply haven't updated their explorer since months.
Therefore you can't click on the addresses, they simply didn't invest a few hours to index them yet.
If you want to view the transaction of such an address, use another explorer. Most of them already support searching/viewing bech32 addresses.
Nested segwit (P2PKH nested into P2SH; address starting with 3..) is 'kind of segwit'. To be more precise, it is legacy data fetched into segwit format.
I guess you might be irritated and refering to it as camouflaged because you can't click on the address ?
If so, this has nothing to do with the address format itself, but with blockchain.com. They simply haven't updated their explorer since months.
Therefore you can't click on the addresses, they simply didn't invest a few hours to index them yet.
If you want to view the transaction of such an address, use another explorer. Most of them already support searching/viewing bech32 addresses.
^^ agreed
I just wanted to link to one of those explorers that supports bech32: https://bitupper.com/en/explorer/bitcoin/
It's not mine, but i like the way this guy is starting his explorer so i wanted to give him some support.
BTW, in this case it probably has nothing to do with opening or closing lightning channels, the values are to large, at this moment most segwit implementations only allow channels funded with up to 0.16 BTC (IIRC)
