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.
648b36f54b1d9d3f39c834a8eef5158e3c94f14424689b2cb18d1a2fff15f9aa
Both payments are on their chains and locked to the same secret hash a55d21e29443d2caf88a0182d2ac634de608c1c8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 648b36f54b1d9d3f39c834a8eef5158e3c94f14424689b2cb18d1a2fff15f9aa
- MakerPaymentSpent: f23910ed47cda9c5ab8f83414e3f5264d3d08eab1f5ab5c8f520f431995be6b5
b0d59a66163d0f1aef0c0259087bf353075fb450f609a535bb84530789cbc0e2
Both payments are on their chains and locked to the same secret hash a55d21e29443d2caf88a0182d2ac634de608c1c8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3320e0d52b44719509ae64d73e463d528ed17fd7f357d14abd16dd6e1683566a
- TakerPaymentSent · TakerPaymentReceived: b0d59a66163d0f1aef0c0259087bf353075fb450f609a535bb84530789cbc0e2
- TakerPaymentSpent: ca9fe834f3c4bc52edf059e9dc529c38607e597aaabc54424c10cda118fb2938
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.