I read here: https://docs.polkadot.com/polkadot-protocol/architecture/system-chains/asset-hub/#track-xcm-information-back-to-the-source:
Track XCM Information Back to the Source¶
While the balances.minted event confirms the arrival of assets, there may be instances where you need to trace the origin of the cross-chain message that triggered the event. In such cases, you can:
Query the relevant chain at the block where the balances.minted event was emitted.
Look for a messageQueue(Processed) event within that block's initialization. This event contains a parameter (Id) that identifies the cross-chain message received by the relay chain or Asset Hub. You can use this Id to trace the message back to its origin chain, offering full visibility of the asset transfer's journey.
What can I do with this Id parameter? it doesn't relate to anything on assethub/polkadot/parachains explorer
I read here: https://docs.polkadot.com/polkadot-protocol/architecture/system-chains/asset-hub/#track-xcm-information-back-to-the-source:
Track XCM Information Back to the Source¶
While the balances.minted event confirms the arrival of assets, there may be instances where you need to trace the origin of the cross-chain message that triggered the event. In such cases, you can:
Query the relevant chain at the block where the balances.minted event was emitted.
Look for a messageQueue(Processed) event within that block's initialization. This event contains a parameter (Id) that identifies the cross-chain message received by the relay chain or Asset Hub. You can use this Id to trace the message back to its origin chain, offering full visibility of the asset transfer's journey.
What can I do with this Id parameter? it doesn't relate to anything on assethub/polkadot/parachains explorer