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.
ec3899f3e3632052d9a8eaebe7651587df5f42ba0044e82e4842a459b8323a98
Both payments are on their chains and locked to the same secret hash 4792f2dcc97e1fe79971301206419d237d225fa9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ec3899f3e3632052d9a8eaebe7651587df5f42ba0044e82e4842a459b8323a98
- MakerPaymentSpent: 665a465934f75f9f82a62258911443557329fdcbe92183e857a2b1d81e162061
312dce693f06da1d5c67d3350012ae1d05ef0ed1e887fc392b0b2223083ddbf5
Both payments are on their chains and locked to the same secret hash 4792f2dcc97e1fe79971301206419d237d225fa9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2200042918f7d415c95e1e34b8a782b443792aa3d542bd71b592f4ef337fbae4
- TakerPaymentSent · TakerPaymentReceived: 312dce693f06da1d5c67d3350012ae1d05ef0ed1e887fc392b0b2223083ddbf5
- TakerPaymentSpent: 0e221b1f9543daadc7e38d011b475b3d70dcc27da4f4dd6654b66c466ef08560
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.