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.
6ae2d05120f82d9f553338fe6a98e16e641f19c127dfa5ba66517a8d6e8bd82b
Both payments are on their chains and locked to the same secret hash 9389d38444659be10a1af14a4edc8aba9396e2b6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6ae2d05120f82d9f553338fe6a98e16e641f19c127dfa5ba66517a8d6e8bd82b
- MakerPaymentSpent: ad0915c1dc613c1a5d7da1b6cc6000ef13493c34f01804a81ffe3fa6ae1b55a2
9e0dfd82f05753af8be0d5cda77f7570d5dc6a716fbb07f076be2bb6fe73ae3b
Both payments are on their chains and locked to the same secret hash 9389d38444659be10a1af14a4edc8aba9396e2b6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b52fdadd5d56a2c7ffabc819a4f086719267e7e8391936348a3d0658645dce06
- TakerPaymentSent · TakerPaymentReceived: 9e0dfd82f05753af8be0d5cda77f7570d5dc6a716fbb07f076be2bb6fe73ae3b
- TakerPaymentSpent: 223813704021bce8b0821f259ebb4f60f0029c862f49394b0cb2d39dacb795a7
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.