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.
856b17e00d063181995a6258424b11cc6b71ed4981225f9a262f1968de7157aa
Both payments are on their chains and locked to the same secret hash 2764af8956d793864582c768c6a9de358861ae7c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 856b17e00d063181995a6258424b11cc6b71ed4981225f9a262f1968de7157aa
- MakerPaymentSpent: 2782e54693c040220111166eaa8fbc5003d31f98e2a46548e76080e97c08bd97
06bc8a7c29ed32ab4909f76b0de8a9b0124188c4d83bb0231c72213c416afbd7
Both payments are on their chains and locked to the same secret hash 2764af8956d793864582c768c6a9de358861ae7c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 70487b8f79c04a9de656fd5ced514e5f4362dc367b41f9fe9b8a9e389763a4e0
- TakerPaymentSent · TakerPaymentReceived: 06bc8a7c29ed32ab4909f76b0de8a9b0124188c4d83bb0231c72213c416afbd7
- TakerPaymentSpent: b22e36a73bb51ee68d80af3321aade07952f7428d5ca1cc3f485c52b9976fbb0
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.