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.
8537dc6d090888bd92f5218f921c03f293ff124a048b1fbe490c866501539878
Both payments are on their chains and locked to the same secret hash 002125e3ff59b33ad3cc8c8523424ed4af58fa94, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 8537dc6d090888bd92f5218f921c03f293ff124a048b1fbe490c866501539878
6966be4557e6f2b4e10d9cd93c153105240dd8262a0d346685a74597b06dd661
Both payments are on their chains and locked to the same secret hash 002125e3ff59b33ad3cc8c8523424ed4af58fa94, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 21af750f46c2a2e731770acaf7a0485bbe4b996ed4ead66f4fd52a613166e60e
- TakerPaymentReceived: 6966be4557e6f2b4e10d9cd93c153105240dd8262a0d346685a74597b06dd661
- TakerPaymentSpent: 84476d963e414dcbdc25ea124ac25bbdd5e7dd0fd9d0f9aa1109f1125cba7be5
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.