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.
e025d2024fe1d6faef745257f180f6ebbda1cf9a2dcc098204bce9505a45e72d
Both payments are on their chains and locked to the same secret hash 540a130ecf989e89a85f5af945afbe7871a809dc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: e025d2024fe1d6faef745257f180f6ebbda1cf9a2dcc098204bce9505a45e72d
24acad8955b03261d12997597ac47fb6dd6db32d13651b5d9fbb517e70a7e348
Both payments are on their chains and locked to the same secret hash 540a130ecf989e89a85f5af945afbe7871a809dc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 2d10c1c3f9f650e6bd7afd89a6b4296208c16cceb4b75975a5f598535041d75b
- TakerPaymentReceived: 24acad8955b03261d12997597ac47fb6dd6db32d13651b5d9fbb517e70a7e348
- TakerPaymentSpent: af1e6d63c694dce0046d7234f1ee7d9b63ea979ee4c9481c5f9bd0cda3b4f628
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.