An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
602cbfa4563ccc754b11ba3515079ea0d74c65be99206737b6f20f0d789a7f78
Both payments are on their chains and locked to the same secret hash f4252d29b4b3f40506ba67a050eb3914ec7218b8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 602cbfa4563ccc754b11ba3515079ea0d74c65be99206737b6f20f0d789a7f78
- MakerPaymentSpent: 8bbaec29522a805fb8a8a3e7640376e4f534dd833e1b4b85dfb9de53c1b84815
9c576891b76c628e682acd22a144e5db671c952a115648fb9c196c4b8c8bf93a
Both payments are on their chains and locked to the same secret hash f4252d29b4b3f40506ba67a050eb3914ec7218b8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 39b6b1d7b3790a74c9443f37fef3aefedbe27e23c000a60485f7f97c7e8a65e9
- TakerPaymentReceived · TakerPaymentSent: 9c576891b76c628e682acd22a144e5db671c952a115648fb9c196c4b8c8bf93a
- TakerPaymentSpent: 3161f183b4f128c6fb14eaaacc4babfc1cf337f3cce88b96938fa594d145e0f3
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.