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.
438ea3858a5137629a18c0021fb140007006811f5ce072115dc9df6db972e42e
Both payments are on their chains and locked to the same secret hash fc0d8ba7aea227af97a1de6b18ac3b2a49619e8c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 438ea3858a5137629a18c0021fb140007006811f5ce072115dc9df6db972e42e
- MakerPaymentSpent: f87b9fa92e2958e44a1dfdca751ab9861b7c07fbc496f76339ab8801f42b78df
e06bf250e987c1640515d62db2b3ddb250b7e1626696743dea53c3cc51a8dc17
Both payments are on their chains and locked to the same secret hash fc0d8ba7aea227af97a1de6b18ac3b2a49619e8c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2faf7dc7267845ec3b5775ea5e96087e4c58b343d2adc074261192f667ce3127
- TakerPaymentSent · TakerPaymentReceived: e06bf250e987c1640515d62db2b3ddb250b7e1626696743dea53c3cc51a8dc17
- TakerPaymentSpent: b5499caa1f5335629e81776f29b1f5c2bab55af3b08bdb49eabf6ef90a8d9c9a
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.