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.
9fb546d1fba02ef58f6ba09bf48a176e9e9ee31e0c9e047dbdfe824e35268358
Both payments are on their chains and locked to the same secret hash 104b39195cfbdf8252f0b263492f8fac05564247, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9fb546d1fba02ef58f6ba09bf48a176e9e9ee31e0c9e047dbdfe824e35268358
- MakerPaymentSpent: 78971c40159151c1036ce3caf98d9d3035c71c4a38acad84c172b9090352c05a
212886ca042cea97c0a3e529b9fe48aa661b9f73899f028b481cffe0b0dc9d03
Both payments are on their chains and locked to the same secret hash 104b39195cfbdf8252f0b263492f8fac05564247, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 919a857c77f880f3bc52d7a67d76642908bb03be725f13539bf18d33d9a63061
- TakerPaymentSent · TakerPaymentReceived: 212886ca042cea97c0a3e529b9fe48aa661b9f73899f028b481cffe0b0dc9d03
- TakerPaymentSpent: c0a533790f6adacdc717496005a0df71599a9b274838581670458a3a5d532d9d
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.