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.
3e912b7e16f4a2f4a931622569ff69d898ecf4fd6ea11aec87b03babd3287070
Both payments are on their chains and locked to the same secret hash 82ed97954b28b66a9ce20be0c8ebd529c5113d71, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3e912b7e16f4a2f4a931622569ff69d898ecf4fd6ea11aec87b03babd3287070
- MakerPaymentSpent: b18267b7da2e02fc331525c581f2b7a5b43a1888c71ee23234a640053192e40d
62ea25a107640eecf681d8cf053284231738892da170ee4b75713205c37b12fb
Both payments are on their chains and locked to the same secret hash 82ed97954b28b66a9ce20be0c8ebd529c5113d71, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: ca1188ce153d61461d9e4702b40cf6ecc158052a8f9c218c39708c07d9b6e039
- TakerPaymentReceived · TakerPaymentSent: 62ea25a107640eecf681d8cf053284231738892da170ee4b75713205c37b12fb
- TakerPaymentSpent: 8d5c434a0a4d6ed49f32ad170785a0a1cd75751a25e926656a33a3e9bdd80be2
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.