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.
cc78645d41a418ca960326b3a005db2316159705595ea4c33dc1847ac5e7fdc9
Both payments are on their chains and locked to the same secret hash ac09dca4e8bf17b705ba6d4892be08903b3641e6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cc78645d41a418ca960326b3a005db2316159705595ea4c33dc1847ac5e7fdc9
- MakerPaymentSpent: 2c9864b6572965776746d3a9b9c1d3f65b9c16ab32e59d74fcba1d9d4312b2ca
172b948e72efd27ca00a873bdda42f76dd43a44808a334f100ddf9caf9734408
Both payments are on their chains and locked to the same secret hash ac09dca4e8bf17b705ba6d4892be08903b3641e6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 915624acda19dcd0d5308cbde1629d09ccca359ed30570a2e5246b03269fcddb
- TakerPaymentReceived · TakerPaymentSent: 172b948e72efd27ca00a873bdda42f76dd43a44808a334f100ddf9caf9734408
- TakerPaymentSpent: d5a758930d60ab67812ad0ecdb9e5b2c7362916db15beb843df231dee611fa01
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.