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.
c66371a592091df0bc3b08f7c2e22a1618efbdd78b5c1dcb3bc0a68edbcc9f1a
Both payments are on their chains and locked to the same secret hash 61318c7bd2e41354f062a6fafad3a2c81f0bfb84, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c66371a592091df0bc3b08f7c2e22a1618efbdd78b5c1dcb3bc0a68edbcc9f1a
- MakerPaymentSpent: 2fd0b1fe378f698241c03484c7899c63a824a2e765b2f8e2e01586a0ff2ffc77
21daeb50b9b34649dada528becd29c1353513e46d408f024eb47cf3450e4081b
Both payments are on their chains and locked to the same secret hash 61318c7bd2e41354f062a6fafad3a2c81f0bfb84, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5f7d9c1fe89f34ae7bdb0a4961a5ee39d882ac0a406421831fb050f3157c9c35
- TakerPaymentSent · TakerPaymentReceived: 21daeb50b9b34649dada528becd29c1353513e46d408f024eb47cf3450e4081b
- TakerPaymentSpent: 401aafc26fa413a788b71ee56a0fa020e6d391ab603c76aac9796e19daf87527
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.