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.
9e159cb1ed40b2f951578e090b76d16764e3e43fb7b175a0e4e5290ef54f3992
Both payments are on their chains and locked to the same secret hash e9d2b95977a881202f71eddbe426272c3ef40e7e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9e159cb1ed40b2f951578e090b76d16764e3e43fb7b175a0e4e5290ef54f3992
- MakerPaymentSpent: ce5d48a78cd98d5988dc07e35d7194000db117784b8c33f22153d58e6755f80e
5744047d22f827ce4203544fc80de50d43b84309e4d273c6a926c27d56049cb0
Both payments are on their chains and locked to the same secret hash e9d2b95977a881202f71eddbe426272c3ef40e7e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a9782dd0e05013ef5ea9442ab4484b82561be2483889ef7fe70371d1622a008c
- TakerPaymentSent · TakerPaymentReceived: 5744047d22f827ce4203544fc80de50d43b84309e4d273c6a926c27d56049cb0
- TakerPaymentSpent: 326bd6446afa9306b4d49cf27bac201356d26f220df7888fd489f4b5cbfef59d
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.