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.
6f33fdd2bc58b9259f935005fefb35735e66e6ee9c7e061c8183992a6ea3d455
Both payments are on their chains and locked to the same secret hash 249d6bf7a5cb540edb588ddd86145987964216f3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 6f33fdd2bc58b9259f935005fefb35735e66e6ee9c7e061c8183992a6ea3d455
- MakerPaymentSpent: 7e8f28fa015e0dacd30e369671c8e5f60ec63c60ee3f1147dfd1203fb182793a
2c3602175c784f0800f07227b780c1a058b5df0de2e1c1adbc2ca3c69006b57e
Both payments are on their chains and locked to the same secret hash 249d6bf7a5cb540edb588ddd86145987964216f3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 43df93a81bb0971a29c40efbb9fc613aa87607d212687a2ae7236eda9c1eab3d
- TakerPaymentSent · TakerPaymentReceived: 2c3602175c784f0800f07227b780c1a058b5df0de2e1c1adbc2ca3c69006b57e
- TakerPaymentSpent: 524fedf7f72ea8323d4fc4bd9824c35de53fe0ac9be7fdce7103ce550dcd5420
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.