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.
0837d46024a551fedea6cd460d25ff4506c42a68915d7cb857153242110e4bce
Both payments are on their chains and locked to the same secret hash d734c2b015e907087e59878b96acccaa53e2032e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 0837d46024a551fedea6cd460d25ff4506c42a68915d7cb857153242110e4bce
992cfd7cebb7cd2084fe531ed88ccf493867babc1f2a7efa45ecc891346090ad
Both payments are on their chains and locked to the same secret hash d734c2b015e907087e59878b96acccaa53e2032e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 1612bef19f5c7d08b976787ed2492597baf01db5905a77ef5c009a134a3932e9
- TakerPaymentReceived: 992cfd7cebb7cd2084fe531ed88ccf493867babc1f2a7efa45ecc891346090ad
- TakerPaymentSpent: f0230adb164ed4be87cde3eff11b2c3fc4143944644ac65bd24bb9464b88823c
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.