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.
1c40d36cb3c5294daac43e70288097434eaf86948bd39fdfa3cc0d2fb89c28ee
Both payments are on their chains and locked to the same secret hash 9a0924dec2209b8746019029675a26cf778bff71, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1c40d36cb3c5294daac43e70288097434eaf86948bd39fdfa3cc0d2fb89c28ee
- MakerPaymentSpent: 8c740bacd2e6f9536513e727184267e0266aa084f48c07f088e22b06cfefe98b
a125502dc97ade1cb6d90cecc06de091fbc96f9b081afd6fa40f645e19f20eb9
Both payments are on their chains and locked to the same secret hash 9a0924dec2209b8746019029675a26cf778bff71, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 44d311a084751c82326f30b43960b76b4e1df112443355146d760da2b226bd2e
- TakerPaymentSent · TakerPaymentReceived: a125502dc97ade1cb6d90cecc06de091fbc96f9b081afd6fa40f645e19f20eb9
- TakerPaymentSpent: 52fce3797acf3ea47cbc53757c8ddbe5a205c900ab87d7281b7379e0a62180e5
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.