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.
cf3ccf2ff272a89ae7d177259ca5d8a12d852a98f1511d01edb0e1b6a76ad993
Both payments are on their chains and locked to the same secret hash f8e09ec51731040c5ca58561c3bc4c3a8c625b59, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: cf3ccf2ff272a89ae7d177259ca5d8a12d852a98f1511d01edb0e1b6a76ad993
19b09225caba3a4eba4b4fa87f3450320cd4f83259076df0cbc59b534dfd969f
Both payments are on their chains and locked to the same secret hash f8e09ec51731040c5ca58561c3bc4c3a8c625b59, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 5b64c7dbce8059cc67fbb236404ef4bdda8ee58d2e058a373c2d2a7654d6e9c6
- TakerPaymentReceived: 19b09225caba3a4eba4b4fa87f3450320cd4f83259076df0cbc59b534dfd969f
- TakerPaymentSpent: 658d13272f96f7bb47827c93b48d71cd13db6a3813e5c91f69a7784b329b8100
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.