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.
dad20b6b1930567e6af47b0eca73ae2df4e513f8fdb0b3fca9fe2bf7fe9a223e
Both payments are on their chains and locked to the same secret hash 066952cc006fc624693d396ec3031e6398a0bfa3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dad20b6b1930567e6af47b0eca73ae2df4e513f8fdb0b3fca9fe2bf7fe9a223e
- MakerPaymentSpent: 1b628f7dd63d9ec9e13b35de34966750e9828f1111f9dd4eb8606b77af9b11ed
9277dd7526fcdd7e32e6b81eb369e10097a6a1f455b020cd817c664343c38225
Both payments are on their chains and locked to the same secret hash 066952cc006fc624693d396ec3031e6398a0bfa3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3edf2283ee20b952c16b72ed116bedea1b06ca45f89a56d4dd44348383280389
- TakerPaymentReceived · TakerPaymentSent: 9277dd7526fcdd7e32e6b81eb369e10097a6a1f455b020cd817c664343c38225
- TakerPaymentSpent: 57344c61606887fd2b489c950b46dd965897fdffe97dc110aac65f57051c6638
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.