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.
d2a2c5aebcd0af4c1b585ac29174ffd5cca7604385c3fe35d0a7c54da47f2be4
Both payments are on their chains and locked to the same secret hash 3fad3470f7a9c6d2b5a3791da4529b0bcb55da85, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d2a2c5aebcd0af4c1b585ac29174ffd5cca7604385c3fe35d0a7c54da47f2be4
- MakerPaymentSpent: db79f2dacf9a1e0ca4fc06ee137cf708fb7296d7e781bc5a1d38714ff609b03c
1d64e15368b1f57e7af2db390cca87eb4653dc299276600b768b5fa086f692a7
Both payments are on their chains and locked to the same secret hash 3fad3470f7a9c6d2b5a3791da4529b0bcb55da85, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 493b724cb2206e6aefd06469b40778db4d4b6297655ac6f8ad3a7cc448d920c3
- TakerPaymentSent · TakerPaymentReceived: 1d64e15368b1f57e7af2db390cca87eb4653dc299276600b768b5fa086f692a7
- TakerPaymentSpent: 5217ee303487d5d049f0cb971b2c0220d4d93093529ab437fe03d0fc5e6ef6af
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.