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.
d02991d382d2571c9609941b062a17c1fae62b71ad93c298ab94a4b3c1844a65
Both payments are on their chains and locked to the same secret hash 9552696a2534b03e11209bb4ba45a9d31c635571, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d02991d382d2571c9609941b062a17c1fae62b71ad93c298ab94a4b3c1844a65
- MakerPaymentSpent: 831911a03994cdd6382a7b652b476eb9656d53f760f55a699bfaba86c2fa1aed
bddb12a4f1006d265f80e7133eb97382ca09b50762a5990a531e5c9a134f669c
Both payments are on their chains and locked to the same secret hash 9552696a2534b03e11209bb4ba45a9d31c635571, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 78c30de5b6ddc4672e61b3ff44c1006e2a7c20b492966b1b50150d416a84020d
- TakerPaymentSent · TakerPaymentReceived: bddb12a4f1006d265f80e7133eb97382ca09b50762a5990a531e5c9a134f669c
- TakerPaymentSpent: ed01d3dc87d698b7a28c861121033c12e5338d8d0ce46643262506c0fc38fa4d
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.