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.
a601039e113dff9ac5859970572fc264efa412a2372e701a513bc79a40266185
Both payments are on their chains and locked to the same secret hash 15c8abaab00e597f50bd298776407190b8b4ec17, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a601039e113dff9ac5859970572fc264efa412a2372e701a513bc79a40266185
- MakerPaymentSpent: 4b0edf6d9f6e7fe2318f221f31e13f9137b81e14e6abb5ed8730cb4853a0f299
5306276e9710a8e43f0f96781c7a6aa4eff1441cfbb8ae551d12df019ca3602a
Both payments are on their chains and locked to the same secret hash 15c8abaab00e597f50bd298776407190b8b4ec17, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dfe10160b8e690d2fba5ea439afcbcea33850f697ee26cc9708e9f0096d38aeb
- TakerPaymentReceived · TakerPaymentSent: 5306276e9710a8e43f0f96781c7a6aa4eff1441cfbb8ae551d12df019ca3602a
- TakerPaymentSpent: 06e548c31056b42456dd9dc8e6fe2257050b46d3e7f34ab072d7302b9b5bfcef
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.