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.
7ebcb09846f0e4d696d0e962b832c42f22f27432967faea20702a83c7e780dea
Both payments are on their chains and locked to the same secret hash 35cd2ed31ce6dc86ba187069fba7a9be59c5f88f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7ebcb09846f0e4d696d0e962b832c42f22f27432967faea20702a83c7e780dea
- MakerPaymentSpent: 6d1bdc3a67416e279873a9c5627eae26fc3448b88ff6f9450b3042377ae61294
a9ec978bbca80da7a4a6f6b143c5ef3b278d6802d0e4da6332db6f40e3274eca
Both payments are on their chains and locked to the same secret hash 35cd2ed31ce6dc86ba187069fba7a9be59c5f88f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d84fb9e8cec8b18883ab227d6e2b08c5d51243319cc0a57be1fbb65a1e41e268
- TakerPaymentSent · TakerPaymentReceived: a9ec978bbca80da7a4a6f6b143c5ef3b278d6802d0e4da6332db6f40e3274eca
- TakerPaymentSpent: 0c28f774ecfa9c455ab93095501ebbc4df6a2771241fd8c3c0a2ec17f0bd0dd7
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.