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.
b88b1d814d8871e5019b53e19f3f6609b78bbe314d0db4c0cf8f851b88d6cc06
Both payments are on their chains and locked to the same secret hash 46f56dd6c76edecb60e5c7121f38ad667d1747fc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b88b1d814d8871e5019b53e19f3f6609b78bbe314d0db4c0cf8f851b88d6cc06
- MakerPaymentSpent: 34e603a295163527c78177bdddbd917dee3cd5b4fa18170fca62fa575eb57829
718aa0512de1b6be6e64393c67a02072692ad0a2f32db4d7f9b5709de40c0e15
Both payments are on their chains and locked to the same secret hash 46f56dd6c76edecb60e5c7121f38ad667d1747fc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 46309b726761e43c29aee74bad2999b0e64e5c07116e13fab26dab8f2ea8ab15
- TakerPaymentSent · TakerPaymentReceived: 718aa0512de1b6be6e64393c67a02072692ad0a2f32db4d7f9b5709de40c0e15
- TakerPaymentSpent: f1a5e636a8fe6607b1621edc355874e380f8fdd703dc60f81f0362285d1c9fd3
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.