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.
cd7e2396a42b253c316d6fab14d27fe46435c242f55ccf2b3f467e4491b61d27
Both payments are on their chains and locked to the same secret hash bd89836af7f85f5687c55d002572f74529f26dda, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cd7e2396a42b253c316d6fab14d27fe46435c242f55ccf2b3f467e4491b61d27
- MakerPaymentSpent: c699698cb5baa613b78d4061284c8ab056ee6047f205ddef45dbc939e269b252
b5a81ae41aedb401516561599eaf1785fb778749ce7949424eb120ac81b392ac
Both payments are on their chains and locked to the same secret hash bd89836af7f85f5687c55d002572f74529f26dda, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5a8c279361f4b8ce6f92a3301ec3c0ea85c1c32564f79fe095aaf07dcd6fa8ae
- TakerPaymentSent · TakerPaymentReceived: b5a81ae41aedb401516561599eaf1785fb778749ce7949424eb120ac81b392ac
- TakerPaymentSpent: c5f537cfdc76b5d9b0491e5506da589d945bd3eef8151efeecd51b40b072e6a1
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.