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.
2e61e11ed6ae3d78b0fbfee6a7406d8a280f265056b2b43425dc059c5e34cfb5
Both payments are on their chains and locked to the same secret hash b523719d063c3836f890ea7d38e429a19a7e4096, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2e61e11ed6ae3d78b0fbfee6a7406d8a280f265056b2b43425dc059c5e34cfb5
- MakerPaymentSpent: 76735cfeaa102b9c61d12e3967350386536dd6d72fd26930445398ab1298bbcc
f1f425e44f351dac214afbaea3b1632e14db7e284d89269356c0e8434d2b1c20
Both payments are on their chains and locked to the same secret hash b523719d063c3836f890ea7d38e429a19a7e4096, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3ba594b29ac1c79f0af4024785a4bb721a9c9418eb52fc7a202b72fdef614682
- TakerPaymentSent · TakerPaymentReceived: f1f425e44f351dac214afbaea3b1632e14db7e284d89269356c0e8434d2b1c20
- TakerPaymentSpent: b16aba7f11546d9f305c703ebf875e6098b2f05e77b8acfa55770e48d4f290c4
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.