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.
8b3d1c6d5325b99d668f1f3b0a2a630d977544ee04595aee71b23915ece5a4bd
Both payments are on their chains and locked to the same secret hash c7335840cc4819188fcb8d7d866c1dc439bb3247, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8b3d1c6d5325b99d668f1f3b0a2a630d977544ee04595aee71b23915ece5a4bd
- MakerPaymentSpent: c77ba5abc1a2465e7156ab5031645a1f9f08983e5b1f92998b0f797acc8a9b46
b3f73c1649052ac22363e4d4f1342ecf423ce96f3f394e0a4b27d48e917407eb
Both payments are on their chains and locked to the same secret hash c7335840cc4819188fcb8d7d866c1dc439bb3247, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 63ebdd78c8bc2b339f22b531ee3cfe4920e3cfa0245863915f41ad35d1684ae3
- TakerPaymentSent · TakerPaymentReceived: b3f73c1649052ac22363e4d4f1342ecf423ce96f3f394e0a4b27d48e917407eb
- TakerPaymentSpent: 5fc349e4512ed0719b67dd2477b3c7b9dac65a9f2f5e7020ec56b2a03e978406
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.