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.
90a959cef050d4bc2885c67204207da585912691320ad06d52bc2c2a37029fcf
Both payments are on their chains and locked to the same secret hash 03734c1085b6ad7ffe8c1a40b39e1a90d839281f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 90a959cef050d4bc2885c67204207da585912691320ad06d52bc2c2a37029fcf
- MakerPaymentSpent: e32f2d01dcba7029ece15480298daec36996888a010a442495dd8fc03ee6bffc
8e72c5a98dd7679514856a1c4969c03d1a810e5370d36cbbefaaaca36641111a
Both payments are on their chains and locked to the same secret hash 03734c1085b6ad7ffe8c1a40b39e1a90d839281f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e31bb2042fc56d0508ce17b7a0f7686682cbbf9857bdb467b6a1ae0bf9473070
- TakerPaymentSent · TakerPaymentReceived: 8e72c5a98dd7679514856a1c4969c03d1a810e5370d36cbbefaaaca36641111a
- TakerPaymentSpent: 68f9d736e286a72aacd37ec85a58e4bcc311ab2c19934afeda090ea325fbebbc
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.