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.
d7b5cbddd3a6d64fd3c5dbc4b289c43053beaeb74bb14dee8cf5496da026c420
Both payments are on their chains and locked to the same secret hash efb0541c7b8b8659cfef090d2e32d325e6c965af, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d7b5cbddd3a6d64fd3c5dbc4b289c43053beaeb74bb14dee8cf5496da026c420
- MakerPaymentSpent: 9df1044197104441fb2c298bb8778bed83416ddb17fc8d808deb7a7a1ca72d9b
563f11796ee25b00f361260ebe2eb63fbb0978cafeb9670bef5654bdeb50efb0
Both payments are on their chains and locked to the same secret hash efb0541c7b8b8659cfef090d2e32d325e6c965af, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 100128a565ff306f702ca25e3ed607f63efc1c3c84255ae4c08a0fd1a72df9ae
- TakerPaymentSent · TakerPaymentReceived: 563f11796ee25b00f361260ebe2eb63fbb0978cafeb9670bef5654bdeb50efb0
- TakerPaymentSpent: 8a6ba866c2cc44b41ce844c266b8820fa51757ae98f062740ba212b49505940a
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.