Okay 
So I am not able to check that transactions outputs are P2SH-Multisig ?
not by only having the output alone because it is the hash of a redeem script which can be any script including a multisig one. So I am not able to check that transactions outputs are P2SH-Multisig ?Quote
Could you explain what params "ps2h" and "p2sh-segwit mean ? What are these two addresses: "bc1qyk02vqmpx8m4l6urmdug9h744y0mn08tkfcw8shk3xgu2jnyktwqnxdsjq" and "389rC5x48fCbcmsWirjyGorUsS4mf7Ldwx" ?
the "decodescript" command is taking the redeem script and converts them to 3 different pubkey scripts. * one is called P2SH which is RIPEMD160 of SHA256 of serialized redeem script (aka HASH160 of it). and its format is OP_HASH160 <hash> OP_EQUAL. the corresponding address is 3FuqMT3VeyRhB917aiJUeWSn2jRt4M3hw8
* another is P2WSH which is similar to P2SH but using SegWit so it is SHA256 of serialized redeem script and its format is OP_0 <hash>. the corresponding address is bc1qyk02vqmpx8m4l6urmdug9h744y0mn08tkfcw8shk3xgu2jnyktwqnxdsjq
* and finally the nested SegWit or P2SH-P2WSH which is like a combination of the above two. it is using SegWit while being "nested" inside a backward compatible P2SH script. its pubkeyscript format is the same as P2SH but the script that it hashes is a redeem script that is created using SHA256 hash of the original redeem script with this format: OP_0 <hash> and its corresponding address is 389rC5x48fCbcmsWirjyGorUsS4mf7Ldwx