No, you can only tell by the input.
A P2SH-multisig output will look like any other P2SH outputs: HASH160 of the redeem script.

Example, use the "vout" of the decoded transaction in ETFbitcoin's post:
P2SH outputs will look like: OP_HASH160 RIPEMD-160(SHA256(RedeemScript)) OP_EQUAL
SHA256 and RIPEMD-160 hash are irreversible.

If you read the implementation details of BIP-0125 (Opt-in Full RBF Signaling): bip-0125.mediawiki
You'll see that there's no "invalid when the outputs were changed" suggests that it's possible to change the outputs of a replacement transaction.

It's very easy to do if your wallet can create signed raw transactions that can skip broadcast and has coin-control feature.
Electrum for example.

The easiest way is to create a signed raw "send-to-own" transaction before sending the "send-to-the-target" transaction.
That way, you won't be needing extra steps of removing the already-broadcast transaction from your wallet's history.

---

Will a posted guide with images suffice?

A. Create a back-to-wallet signed raw transaction.

1. Open Electrum and go to "coins" tab (View->Show coins), right-click and click "spend" to select a UTXO(s) that's enough to pay the target.

It will be highlighted in green when selected.

2. Get an address from your own wallet and go to "send" tab, paste your address to the "pay to" box and input any amount or max.
Click "send" but do not click the next "send" on the next window, click "Advance" instead.
In the advanced window, increase the fee to an insanely huge amount and make sure "replace-by-fee" is ticked, click "finalize".

A new window will open, here you need to click "sign" (this is a must!):


3. In the same Window, click "Export->Copy to clipboard":

4.Save it to a text file:

5. Then close the window and disregard the warning that it wont be saved by clicking "yes":


B. Send the coins to the "target"

1. If you have closed the wallet or the coin selection was reset, just repeat the step one above and select (one of) the coin that you've previously selected.
2. Send it like a normal transaction but use 1sat/vB fee and you should be able to see it on blockexplorers as well as the other party.


Transaction: 642bf8e3d46591485c5b0d9aef2349123a21378e784c3fac1014e907ac11bb36 (now marked as invalid).

C. Invalidating the transaction by broadcasting the replacement

1. After deciding to replace the transaction, all you have to do is to broadcast the previously created "signed raw transaction" using either the "console" tab (View->Show console) or online push/broadcast transaction service.
For electrum tab, enter:
That includes the quotation marks, the 020000... is the raw transaction that you've saved in a note or text file.

After that it will replace the previous transaction as long as the previous is still unconfirmed, has a higher fee that's enough for additional 1sat/B fee and replace-by-fee was enabled:

Transaction: d5d5300996c661de9ffb4588ae0ac6a0be3ffdccc63d92e37c159f77ec97cbf0

If he has 32GB of RAM and more, there's no harm on using a high cache size.
The problem in the config is par=15 which limits his system on using 15cores while the default "0" will use all available cores if needed.

For the issue, OP might had just started the -reindex when he posted this thread.
At which point that there're no signature validation required for earlier blocks thus wont require a lot of CPU usage.
If not, there must be a bottleneck somewhere.

FYI, blockchain.com in general isn't a custodial wallet.
Their "Buy Bitcoin" service however is custodial because it's tied with their exchange, just like other Buy crypto services and exchanges.

I'm not taking sides but this contradicts the first statement and those problems are from newbies who think that blockchain.com is a custodial wallet.

There are a couple of info within the wallet about not-to-be-able to recover those info since those aren't stored in their server.
Since it's a non-custodial wallet, all those sensitive data is in their own (user's) care,
just like Electrum, no one can directly help you if you lost your seed phrase or forgot the wallet password.

The issue that can be blamed to them are problems with logging in, not receiving 2fa/email authentication, wrong balance, etc.
"Account freeze" can only be done to the trading wallet and only when you bought bitcoins using cards and other matters.

I don't think it's possible to change the derivation path of a Coldcard wallet.json export,
the master public key itself was derived from that derivation path so whether you changed the derivation path in the json file or not, it will create the same wallet.

As described by o_e_l_e_o.
Any machine that's permanently disconnected from the net is considered "Air-gap".
If you don't want to use your seed phrase, you can wait for more replies to have more options;
and use that method plus other derivation paths as the last resort.

First, if it starts with "3", it's P2SH.
On blockexplorers, it's impossible to tell the script just by looking at a transaction with it as an output.
I'm not familiar with P2SH-P2PK (CMIIW) but there should be an OP_CHECKSIG (AC) at the end of its redeem script if used as an input
(shown different per blockexplorer).

The easiest method is to check the addresses on Armory itself,
every used addresses is listed in the "Used Addresses" and "Change Addresses" drop-down menus of "Wallet properties" of ArmoryQT.

---

BTW, last time I checked, there's a reply that you've successfully synced Armory and sent the coins out.

Does the exported file looks like this:

If you've used the top-most xpub for your SegWit export, try this on an Air-Gap machine (always offline):
Since those xpub/zpub have a derivation path of m/ when imported,
Use the 24-Word Seed Phrase and your BIP-39 Passphrase to restore the wallet using the option:
Standard Wallet->I Already have a seed->Options "BIP39", tick "Extend this seed with custom words" if your Coldcard have a Passphrase.
Paste the Seed phrase, click next and type the BIP-39 Passphrase if you ticked it.

In the address selection window, select P2PKH - Legacy, then change the derivation path into m/
Now, check the addresses in the address tab if they match.

Sweep will create a transaction and send the balance of the address derived from the key to one of the wallet's receiving address.
Import will add the key to the wallet, it's only available for imported wallets created by importing keys.

In Electrum's address tab, is it showing the same address(es)?
To open address tab, Click "View->Show Addresses" then click "Addresses" beside "Receive".
Because in Electrum, you can add a prefix before the keys to import the address type that you want.
You can check those prefixes by clicking the "Info" button when importing keys.
But as I mentioned above, it's impossible to import one type of address from Armory to Electrum which is P2SH-P2PK.

Armory shows balance so you should be able to see which address/key(s) to export in "Wallet Properties" in the drop-down menus under "address".
If you've previously done any transactions before, it might be in one of your change addresses.
You can double-click an address and select "View address keys" to export its private key.
Note that it will be troublesome to import the keys if it's in a P2SH-P2PK change address.

Also, in Electrum, did you verified the installer/executable to check if it's the official version?
Did you recognize the last transaction in the history tab?

Do a quick search (upper-right) of the name of the "third party" when viewing this page: https://bitcointalk.org/index.php?board=83.0
If there are a few results, then read the topics.

None?
This may help to figure-out the issue: What are the exact words did he/they said about "confirm the transaction"?

Try to rename the data directory in the same drive as the portable executable, it's "electron_cash_data", rename it into "electron_cash_data_backup" or similar.
If you mean "Electrum", not "Electron" as you said in the OP, the data directory for the portable version is "electrum_data".
That should clear the data directory; then try to open Electrum 4.0.3/Electron 4.1.1.
If it opened, restore your wallet using the seed phrase.

If it didn't worked and you want to return everything else, delete the newly created data directory and rename the original back into "electron_cash_data"/"electrum_data".
You may as well choose to create a backup of that original folder.

---

If it didn't open using the above instructions and your OS is an old non-updated version of Windows7 labeled as "Windows 7 Service Pack 1" in Properties of "My Computer",
then try to download and install the said update, it's required by most app, not just Electrum and you might need it in the future.

Make sure to select the correct version to install: support.microsoft.com/en-us/help/2999226
Specifically, one of these:
You can check if your PC is x64 or x86 (32-bit) in the same window where you can find the Windows version and service pack.

The installer will also detect if you already have it in your PC.

Ah, so it was mined the same way as the block on the final post of your other thread: Is there any online (web) tool where I could broadcast a new block I mined?
I though you've done it the same way a pool operator or solo miner does: a full node and a miner.

Unfortunately, most of them don't like the idea of changing a code in either their mining pool software nor Bitcoin core to include those non-standard SegWit Txns.

Have you tried adding: acceptnonstdtxn=1 to your bitcoin.conf file before sending the transaction?
AFAIK, that should work in testnet/regtest and will allow some non-standard txns to your mempool (what's not clear is which ones).

There's not much info from that image aside from a non-connected state Electrum.

It's best if you can follow HCP's guide above to get the debug.log in order to see what's the actual issue.
Just carefully censor the parts which you do not want to share for privacy reasons.

It's easier to do in tesnet because you can easily set a configuration to accept non-standard transactions to your mempool.
While in mainnet, the config wont work.

IDK if there're other ways aside from changing the code but if there is, someone should point it to kano and other pool operators.
Here's kano's decisive post to reject the bounty: /index.php?topic=5192454.msg53747843#msg53747843

If you've sent enough funds and your channel tab shows "can receive x.xx BTC",
you can use "submarine swap" to increase your lightning funds up to the available inbound capacity.
To perform "swap" in Electrum, click the "swap" button and click the lightning logo or the BTC logo to switch them,
then fill-in the on-chain funds that you want to add to your lightning funds and complete the transaction.

Note: that will require an on-chain transaction and third-party service fee so it's not-so-different from opening a channel, moreover, it's more expensive.

Based from the URL above:
It's Binance's internal trades which is what they advertise in their "About" page: https://www.binance.com/en/about

@jademaxsuy it's just a "number" for marketing purposes (not a real time or updated data), it's the average trades done in their exchange, not any coin's blockchain.
And the numbers won't affect the transactions that are being mined nor the transaction in Bitcoin nodes' mempools.

That's why I've said "Bitcoin core with -txidex".
Because that was needed to be able to use getrawtransaction for txs outside of the client's wallet.
But I hadn't explained what it does and how it's applied since I thought the first option was enough and will do the same.

There are a couple of online "Proof of Burn" address generators out there like this one: https://gobittest.appspot.com/ProofOfBurn
It only supports legacy Bitcoin address and you'll likely encounter problems with max number of prefix.

Example of a valid weird address: 3HeyThisisAProofofBurnAddressxrgL7
It's a P2SH address and made using a python tool created by someone else but I can't find the download link.
-Edit-
Found it: https://gist.github.com/CoinWhisperer/6d673f1f3d13da1611cd
Read the comments for the dependencies.