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.
4c4edb7839fad0f128409ba434b12192dc60651daa6c8ee204262062364d30ad
Both payments are on their chains and locked to the same secret hash db22a0ae53e90a0ca53807c89435067a31a7193a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4c4edb7839fad0f128409ba434b12192dc60651daa6c8ee204262062364d30ad
- MakerPaymentSpent: cf1b30060ec5bfcc06b2430068099facbc0d55ad69f1023b05b9d408902e0b6e
2eb36f04797dc45dc334dbd91c5330c057bccf9314c2cf5b52636c8fc749a81c
Both payments are on their chains and locked to the same secret hash db22a0ae53e90a0ca53807c89435067a31a7193a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c8667330f05d1a0affb735a13206703ae1770e803a4b0f3a20d16605c8e3e29b
- TakerPaymentSent · TakerPaymentReceived: 2eb36f04797dc45dc334dbd91c5330c057bccf9314c2cf5b52636c8fc749a81c
- TakerPaymentSpent: 2a66d476555629b67f546ac6ae9dcb5a6967cb65bd84b56651aefe1e92d0723d
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.