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.
5d13a6635d51656ec8be79abd0ab5c7f50a4b32b66372d982aecb55936a3e8b6
Both payments are on their chains and locked to the same secret hash ed782aae55cc053caa5ba1214503eb26483c8f73, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 5d13a6635d51656ec8be79abd0ab5c7f50a4b32b66372d982aecb55936a3e8b6
420ac1e4eea15e9c1484d69e4304c1199e9eb9a94b6d97f2987a9460ff388dd7
Both payments are on their chains and locked to the same secret hash ed782aae55cc053caa5ba1214503eb26483c8f73, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 65888836bfd41112111c5b234ef993f70f726bf82f1a0ca9a870adcc66e471ef
- TakerPaymentReceived: 420ac1e4eea15e9c1484d69e4304c1199e9eb9a94b6d97f2987a9460ff388dd7
- TakerPaymentSpent: 3e18077f0e9850288ac838ad8ca045342473da215913cc7595cdc47c36aab16e
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.