Here is my result:

Summary generated with srtool v0.9.15 using the docker image chevdor/srtool:1.53.0:
 Package     : statemine-runtime v2.0.0
 GIT commit  : 3462a4b7fadb5562bb4000013636ad5be770f18c
 GIT tag     : statemine_v2
 GIT branch  : heads/statemine_v2
 Rustc       : rustc 1.53.0 (53cb7b09b 2021-06-17)
 Time        : 2021-07-22T09:25:05Z

== Compact
 Version     : statemine-2 (statemine-0.tx1.au1)
 Metadata    : V13
 Size        : 1.59 MB (1662655 bytes)
 Proposal    : 0x3fedcd521b990142eb07f5c8a5383ae81373f6778a49d3150bf30dd1a2a0564c
 IPFS        : QmQ5wBHDK2ZEDkjcJZFDHnuirTpDpPenR8NGWfr6cZsz41
 BLAKE2_256  : 0x4b657c806e5c6d9623836c85eadd3f32f68560a29485f44bdcebf4ca4fa6941f
 Wasm        : polkadot-parachains/statemine/target/srtool/release/wbuild/statemine-runtime/statemine_runtime.compact.wasm

== Compressed
 Version     : statemine-2 (statemine-0.tx1.au1)
 Metadata    : V13
 Size        : 473.03 KB (484381 bytes)
 Compression : 70.87%
 Proposal    : 0x3fedcd521b990142eb07f5c8a5383ae81373f6778a49d3150bf30dd1a2a0564c
 IPFS        : Qmd768oEuqNqY4m3EgVg4bGHsXYZH7LuHRS2BwF5GKurQT
 BLAKE2_256  : 0x4b657c806e5c6d9623836c85eadd3f32f68560a29485f44bdcebf4ca4fa6941f
 Wasm        : polkadot-parachains/statemine/target/srtool/release/wbuild/statemine-runtime/statemine_runtime.compact.compressed.wasm

Note about verification. This upgrade is using a compressed runtime and a bug has been found in the current subwasm release. In a nutshell, the proposal and blake2_256 hashes are currently computed on the decompressed wasm instead of using the raw bytes (=compressed) of the wasm.

Since this proposal is an XCM call, there is no hash in subwasm that will match the proposal_hash mentioned above.

The subwasm issue mentioned above has been already fixed and a new release will be published.

Here is the output of the fixed subwasm version:

🏋️  Runtime size:		0.462 MB (484,381 bytes)
🗜  Compressed:			Yes, 70.87%
✨ Reserved meta:		OK - [6D, 65, 74, 61]
🎁 Metadata version:		V13
🔥 Core version:		statemine-2 (statemine-0.tx1.au1)
🗳️  system.setCode hash:	0x025ec7538d168a1baf8404cf116ac338af609aa5822b8058fbc4576233a8c44d
🗳️  authorizedUpgrade hash:	0xa141f359c6d372e7b161ccad870fdca5d84437d10c741206e89e88b3494163e5
🗳️  enactAuthorizedUpgrade hash: 0x26ce6d60465b80e1e56b2609ac7bf3b09201bcb37e0097e473197f4bcd86fd57
#️⃣  Blake2-256 hash:		0x804c97cbf81f12d520204e7b1302603b4232a46ff0f408eea2ef9a9356109187
📦 IPFS hash:			Qmd768oEuqNqY4m3EgVg4bGHsXYZH7LuHRS2BwF5GKurQT (https://www.ipfs.io/ipfs/Qmd768oEuqNqY4m3EgVg4bGHsXYZH7LuHRS2BwF5GKurQT)

We can confirm that suwbasm was ran on the same input (you can check the IPFS hash, which was not affected by the issue mentioned above). In the output above, we can see the proper runtime code hash:

#️⃣  Blake2-256 hash:		0x804c97cbf81f12d520204e7b1302603b4232a46ff0f408eea2ef9a9356109187

This is the value used to procude the XCM call and verifying this value and rebuilding the XCM call in the PolkadotJS UI.

This TC Proposal fast-tracks motion 331 to be voted by the community in referenda queue for the next days.