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.
338bb9c2a5bd3217758940ea7603fd57d4fb9920415d93c1d4de29fe9fbbda20
Both payments are on their chains and locked to the same secret hash 059ce88ef9b742619530547c3c2868150542e2b0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 338bb9c2a5bd3217758940ea7603fd57d4fb9920415d93c1d4de29fe9fbbda20
- MakerPaymentSpent: 221535a353bc3258f9ccadc728aa568ca3916814522986132e609c4070655301
47b09202235ac63a336b44f9e393cd1c51de26684bb2452d2c26d905d0849d74
Both payments are on their chains and locked to the same secret hash 059ce88ef9b742619530547c3c2868150542e2b0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 683c9832138382624045daf0a4dd7406f1d63072b97ee266149c0146d419ffb7
- TakerPaymentSent · TakerPaymentReceived: 47b09202235ac63a336b44f9e393cd1c51de26684bb2452d2c26d905d0849d74
- TakerPaymentSpent: efc4096e13c6e0944d32e00b22e6f09641986613b087dee6303202f4be622d32
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.