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.
9880a310bc93486143fb9ef23868f0a496a9c41e1e354fa515fd426750a6c359
Both payments are on their chains and locked to the same secret hash 4948cb28f486e814385e31037441ce4519a61658, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9880a310bc93486143fb9ef23868f0a496a9c41e1e354fa515fd426750a6c359
- MakerPaymentSpent: 19714ad6cb3edb71209705294e8ff72561b043fea9cf9d1fb67af6db16a610a3
53253332466cd94fe08662f2f193c76e8e0502a99302eae3f7e113e10de81cda
Both payments are on their chains and locked to the same secret hash 4948cb28f486e814385e31037441ce4519a61658, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ad0aa8ddaa75e18d5c91a90a19866d4230c8f6dc398e3e913c729f4e584654c3
- TakerPaymentSent · TakerPaymentReceived: 53253332466cd94fe08662f2f193c76e8e0502a99302eae3f7e113e10de81cda
- TakerPaymentSpent: 6f347013206bd9657e4205dd899b2b2be706c172b9f449e54a0fc0c921ac2217
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.