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.
98fe6fecbd1510fc2786d46aacc52f34d44c022f39cca80c1e15ecb3e7b2e4c0
Both payments are on their chains and locked to the same secret hash 077a413da28736c5372e3eb53abbf24b38de6438, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 98fe6fecbd1510fc2786d46aacc52f34d44c022f39cca80c1e15ecb3e7b2e4c0
- MakerPaymentSpent: 8e7e066cd272ee58020cabbca432d7cf7dd214e7940f9890e6cb0b2b2f4d9060
2bc93b67c04c0dc1736a43e806700fcce11c01767f3b4fbd2224abb9c749f6f2
Both payments are on their chains and locked to the same secret hash 077a413da28736c5372e3eb53abbf24b38de6438, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3352a878b61a1555e1fd2a34ddebb093fd89f4b2d6d63202d58874b9fdaa8b3f
- TakerPaymentSent · TakerPaymentReceived: 2bc93b67c04c0dc1736a43e806700fcce11c01767f3b4fbd2224abb9c749f6f2
- TakerPaymentSpent: bd5b4731fcca280a80a4f6fb8d3e7a9e5e6dc7c2ee4e41750b9e9569b18a13a0
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.