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.
7cf93ee5002637b27843a19e63bc53d38e92da29f2e7a3ecb118dcfa3929ef67
Both payments are on their chains and locked to the same secret hash 65f3b0741ab86601dbdb11628f852401ea765c33, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 7cf93ee5002637b27843a19e63bc53d38e92da29f2e7a3ecb118dcfa3929ef67
- MakerPaymentSpent: b9b3f55a4d80d96686de6319df82b9e06642fbca49d07966f78213afe64fe310
4de7cb3629fdf972eb7865fce5ea187943101d78b9c17ae08d71679a24cccc8f
Both payments are on their chains and locked to the same secret hash 65f3b0741ab86601dbdb11628f852401ea765c33, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: caa9dfc45d22f2740e61b0636aaee60f244ce634d516f5faccba906fd50d2345
- TakerPaymentSent · TakerPaymentReceived: 4de7cb3629fdf972eb7865fce5ea187943101d78b9c17ae08d71679a24cccc8f
- TakerPaymentSpent: 2fb96a147565967b33da6ae53ce2d13d8743c47ca1c86fe5503fbf4f5b0bc6cc
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.