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.
e6a0c7e1aecd67012ed54154fe7e69bf75d37839fca6e4097d5a1d2a9ae78c69
Both payments are on their chains and locked to the same secret hash 6090383cd61a9db4db92873932d478e6d2f2116f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e6a0c7e1aecd67012ed54154fe7e69bf75d37839fca6e4097d5a1d2a9ae78c69
- MakerPaymentSpent: 4a0a59e0cddb7f975d7ad654d13994ad0a9ca619b0ba620fbcd3b69a73cdf88d
587227eb2dccd428487e4db34f1952c547c59cf0982db7d5533012402a025b28
Both payments are on their chains and locked to the same secret hash 6090383cd61a9db4db92873932d478e6d2f2116f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0d53d6d4fa878aec32ff450e013c8423662f43f91489ed307473d8b175c68249
- TakerPaymentSent · TakerPaymentReceived: 587227eb2dccd428487e4db34f1952c547c59cf0982db7d5533012402a025b28
- TakerPaymentSpent: aa7b2594627c7500e08e1ff621cec705795e1f3714be88f841578385fb284333
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.