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.
cc60f6060d080a73d86a1afd3ce73f324f4cf66ed0d89d8d7f8cf3c9a7938232
Both payments are on their chains and locked to the same secret hash 60a5a5063627df7b24ea8837d8f700032c08caf9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cc60f6060d080a73d86a1afd3ce73f324f4cf66ed0d89d8d7f8cf3c9a7938232
- MakerPaymentSpent: 79214c0938bacf5bcf103294f01e1dac0c33f7fabb79774a69e16332a6ce3fcd
69716c03ff09c940671d050a83057d04df5eb7560da85fe950b408e087b504d0
Both payments are on their chains and locked to the same secret hash 60a5a5063627df7b24ea8837d8f700032c08caf9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 55adc5a5c0d3ab409c1fe99f7a6cd38af187d57a5942776ed10be1a57094a5f7
- TakerPaymentSent · TakerPaymentReceived: 69716c03ff09c940671d050a83057d04df5eb7560da85fe950b408e087b504d0
- TakerPaymentSpent: b6f205273ca4678a65b8db0f40f29e1b9d630eebfc060dc5d4d43daa07674c8a
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.