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.
36a249407a4aa9fc5cd843184e663b9e2924a5e7845315aa52313afbdd92d336
Both payments are on their chains and locked to the same secret hash 168e0ecf81c06997f7bee6ba82afaaa0f8dc1dc3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 36a249407a4aa9fc5cd843184e663b9e2924a5e7845315aa52313afbdd92d336
- MakerPaymentSpent: 88fa1475ceb9e6533936beb02a5f2f161f336013f61937d32db0b83351225b6f
bda4bfe8763c46434fdd4c618245d6d40e6f057da70fa4a4fc9e0ee2dc234c96
Both payments are on their chains and locked to the same secret hash 168e0ecf81c06997f7bee6ba82afaaa0f8dc1dc3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a9bc42fe3fd67d00579193c068e2bc13d7a6a12feaffc90a6d395ec94d4ebc0d
- TakerPaymentSent · TakerPaymentReceived: bda4bfe8763c46434fdd4c618245d6d40e6f057da70fa4a4fc9e0ee2dc234c96
- TakerPaymentSpent: 06f8cc465dac47ab4e94d95644b9cbb24a83427a2e64fe0c95c8173ea39ea0ae
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.