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.
382d2aca69cec9a08b8e1e2e4f8f26e242ede4be4addb79ef1a8ae62938ebc73
Both payments are on their chains and locked to the same secret hash a5d3f8c6dd96344f2088b3fb9d7274ccd669081a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 382d2aca69cec9a08b8e1e2e4f8f26e242ede4be4addb79ef1a8ae62938ebc73
- MakerPaymentSpent: 503a018728e1856b108db1ff9c32f37386f39cdeb65c0d61c30bad385c39069f
64a3d9fdfed1c33faa6678ecf4293dd7c7acf9efa07c2bd31aa31af433cdc4c8
Both payments are on their chains and locked to the same secret hash a5d3f8c6dd96344f2088b3fb9d7274ccd669081a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: aa172bd2bc6ffda7c5ebbd136788723ee03aea4a92f9de2a49ad069688d74e4b
- TakerPaymentSent · TakerPaymentReceived: 64a3d9fdfed1c33faa6678ecf4293dd7c7acf9efa07c2bd31aa31af433cdc4c8
- TakerPaymentSpent: 6f5f1db073248cf4a76a567034b9b5f745360969a9271fa7debd94a47db19d1d
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.