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.
7b14ccb6ffca7cd7d81378b6907e1e5b471b423681c819421d2ce40b9db0860a
Both payments are on their chains and locked to the same secret hash 2b98b7df2514b17520761e1bd2c7428bc1acef60, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7b14ccb6ffca7cd7d81378b6907e1e5b471b423681c819421d2ce40b9db0860a
- MakerPaymentSpent: cff552d8fd1094cd1b22006d0bb22c8ad0afbb6bd03474204bb2e4c9ec44928e
1b25821b5e72b32a0b967899b3585e8bf0b0e729d21ae4dd7f7ae7a01ea5b212
Both payments are on their chains and locked to the same secret hash 2b98b7df2514b17520761e1bd2c7428bc1acef60, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 54e21b5815108d3c047e8fa27e71d9088c108ee6bfbd8fcf55bdc194bacf6cfd
- TakerPaymentSent · TakerPaymentReceived: 1b25821b5e72b32a0b967899b3585e8bf0b0e729d21ae4dd7f7ae7a01ea5b212
- TakerPaymentSpent: cb170dd2be65374149662cd018977ea3240dd3b610006fbfc94e6dc58c4663df
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.