In signing with the second one celebration, the multisig script this is your witness script were given tousled.
In each the preliminary PSBT and the primary signing, we see that the witness script is
which is decoded as
2 02dbbedff721dcdc7737c0e931c0473db3aadf4690f01dd5fc6da65188e21ecffd 02f4e91f49be47c24571e100c501cc50e9c499e744a25e51e2153d26b856605952 2 OP_CHECKMULTISIG
This script has a sha256 of
4b29bdce823c1afde68cc26012e49a913fc005a629748afbea7285d7ac281b7c which goes the hash given within the redeem script of the enter, and the redeem script has a hash of
4d3a0d4465e19bb387df92f5e052f24370718117 which goes the hash within the output script of the output being spent. That is all proper.
But if we have a look at the general transaction, the script for some reason why is modified to
which is clearly other from the witness script at the beginning. It is sha256 is
64b235d9fd37f2d68cb6edf19a25cc7765ef9c7299e3b448c86196cecd60feb0 which does not fit the hash within the redeem script, so the script interpreter fails right here.
This script is decoded as
2 02f4e91f49be47c24571e100c501cc50e9c499e744a25e51e2153d26b856605952 02dbbedff721dcdc7737c0e931c0473db3aadf4690f01dd5fc6da65188e21ecffd 2 OP_CHECKMULTISIG
Taking a look at those two scripts, we will be able to see the second has the keys flipped round. For some reason why, the device you used to finalize the PSBT modified the site of the keys within the script, which has resulted within the ultimate transaction failing.