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.
008123d6a5d212fe138ff12a030e8ec06d539d4034103d145c7431dd1554de6c
Both payments are on their chains and locked to the same secret hash 39b12b608fb0d2be41483b0e0a9445746897b105, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 008123d6a5d212fe138ff12a030e8ec06d539d4034103d145c7431dd1554de6c
- MakerPaymentSpent: b4d4a3574188dfceb5aa30a3a8c1ff446f8e161f79078d4d6349c5c5f087098e
145963fcbf459c0dee48b8b8a1de1642ca9d154283ee5424eb65f61270f5265c
Both payments are on their chains and locked to the same secret hash 39b12b608fb0d2be41483b0e0a9445746897b105, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5c697df1a1895560d45e6120e21d0e2dcf7515b8a8ae5cab17a1fc29f3311c52
- TakerPaymentSent · TakerPaymentReceived: 145963fcbf459c0dee48b8b8a1de1642ca9d154283ee5424eb65f61270f5265c
- TakerPaymentSpent: c61895efdd954e138668df967ee31e89b132fd0f388c8253611d21ee02966001
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.