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.
af804fa6de9e738fb333b1dba6dff84b6019253e52df79cb5982e6aacbb5e7ce
Both payments are on their chains and locked to the same secret hash 390982dbe015d08c45442939f16066c8b63fc2e9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: af804fa6de9e738fb333b1dba6dff84b6019253e52df79cb5982e6aacbb5e7ce
- MakerPaymentSpent: c4e451d7053f9a72a7396aa129e1fbaf8cfcbf65534ab47e25ae443eba5f5d1d
31ba2797e3b22a804c7fea921d1b92077cedb8e81feae8def688cef8fa0e381f
Both payments are on their chains and locked to the same secret hash 390982dbe015d08c45442939f16066c8b63fc2e9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5e477c070352d772263e59567518210fb2c07c488fa1f2c195b819f6f790a2e8
- TakerPaymentSent · TakerPaymentReceived: 31ba2797e3b22a804c7fea921d1b92077cedb8e81feae8def688cef8fa0e381f
- TakerPaymentSpent: 7e83742f0f465bbd083a60cd117f53d07421adcab4839e3aa757081dc8f48758
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.