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.
aae53fc214ffb3b23acc995735b0cf075d3f90e439cc12302a8eb35b7ad5d0ee
Both payments are on their chains and locked to the same secret hash a56b1b07553084a443d9ede26c2ae142f21cee01, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: aae53fc214ffb3b23acc995735b0cf075d3f90e439cc12302a8eb35b7ad5d0ee
- MakerPaymentSpent: ff0299210327cc4bc1c9344ec53676b8da45bb37c0cbb5774237350396be12ea
ec24834e95200a0c074738fe2e615971646f01647a8315c1299c07c3baee364a
Both payments are on their chains and locked to the same secret hash a56b1b07553084a443d9ede26c2ae142f21cee01, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b4fce92a481383757b79c4ef7c97149216d00ef4633d9ff68a9b124a3e90813c
- TakerPaymentSent · TakerPaymentReceived: ec24834e95200a0c074738fe2e615971646f01647a8315c1299c07c3baee364a
- TakerPaymentSpent: 51fd0913c49b58cd0dc28609ed9cc4522b1f19a552cb00298fcf4b85e6ea8291
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.