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.
1050fd83ca3054fb7b918a74d3f9e318358b9e9cf2e7582efbba6fc6678ddf6c
Both payments are on their chains and locked to the same secret hash aa2628bc235cfbd5b06786c43935a6a401be04cb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1050fd83ca3054fb7b918a74d3f9e318358b9e9cf2e7582efbba6fc6678ddf6c
- MakerPaymentSpent: 018f7ec1ef4cc65df73e8450e8833d16d5ad37236f1ede0610809ab20c92dd81
05910870922089ecf5223a6dcf59479a43009dddd51e2330a8aa0f52052627d0
Both payments are on their chains and locked to the same secret hash aa2628bc235cfbd5b06786c43935a6a401be04cb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9fddebe868e798330ec3ea6459ed87bc0aad5a3e55245f3d47b17769d1939509
- TakerPaymentSent · TakerPaymentReceived: 05910870922089ecf5223a6dcf59479a43009dddd51e2330a8aa0f52052627d0
- TakerPaymentSpent: 8e06c2f9faf382771404c1f52c572dc7ae82ff6adb5f71aed1334d69c8b172b2
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.