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.
baeee08419db8d032d23bdb02c067da81e10acf16d7b0d632d091c3344dcddc7
Both payments are on their chains and locked to the same secret hash 447f9aa27f60bc8c53f8db31f3fa8049c9fca3a0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: baeee08419db8d032d23bdb02c067da81e10acf16d7b0d632d091c3344dcddc7
- MakerPaymentSpent: c4e86e7b5956ce20f133887311325ad14a452635f02a0dc75b48df282521c29d
095ef48c0d1905739d8d38a1df7a8ec83564dcb5337301a53f43e6b662dfd086
Both payments are on their chains and locked to the same secret hash 447f9aa27f60bc8c53f8db31f3fa8049c9fca3a0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cd2e305c07bdb09b343ddadf43caf83e8f0052ed65cc1036b239ec25e6c427a0
- TakerPaymentSent · TakerPaymentReceived: 095ef48c0d1905739d8d38a1df7a8ec83564dcb5337301a53f43e6b662dfd086
- TakerPaymentSpent: 0aa2665b3dec4ae0e60d5cb8f41fee6eade6269ba0dd6d506de11f426f0740ed
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.