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.
635dcb1e3f5ada9728eb78dc8a38d48937c719160219d7d4142995a7366dbefa
Both payments are on their chains and locked to the same secret hash a607a64c617b548f1a3b72cf2eab3d31d036a3ed, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 635dcb1e3f5ada9728eb78dc8a38d48937c719160219d7d4142995a7366dbefa
- MakerPaymentSpent: 12848f5346052f4fb57433e2c6be53276c8f17e1e241d0a98f018c477c23b9e7
911aae86af0708f0cb9f07258e932140d1d5ff78334f62ddc87b4a423e94aea5
Both payments are on their chains and locked to the same secret hash a607a64c617b548f1a3b72cf2eab3d31d036a3ed, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3f83e56bdfc976ce69b70084224e02bc4165f1995eeaa0258690f53066514f9e
- TakerPaymentSent · TakerPaymentReceived: 911aae86af0708f0cb9f07258e932140d1d5ff78334f62ddc87b4a423e94aea5
- TakerPaymentSpent: 3e7fd72cc2581d0cabd1b8b1812f3a05ba41ed1bc97054109af35e35909719cd
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.