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.
0c2f64398c8aad2d83b1606bd000229279127c5c1ac4edce7c6e454fa14a04d1
Both payments are on their chains and locked to the same secret hash b2235a321832aec9f8223981a00c19d5cc362adf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0c2f64398c8aad2d83b1606bd000229279127c5c1ac4edce7c6e454fa14a04d1
- MakerPaymentSpent: 45f390a3c36dd4937e65a31496952ee0b3a7ad423d6e3478b8745ba1009570ff
75668c9275c4329ba66720e4985566f03db8745dfa7708e4ea9ec2c346957816
Both payments are on their chains and locked to the same secret hash b2235a321832aec9f8223981a00c19d5cc362adf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b254838ca7612fe7b59ce632f02888da65374e768a8a9ecfd2e43696533d1add
- TakerPaymentSent · TakerPaymentReceived: 75668c9275c4329ba66720e4985566f03db8745dfa7708e4ea9ec2c346957816
- TakerPaymentSpent: 67536c474120e52a9bbdee9aab557d97ffbb62b06cc567e56852e0bd07807b27
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.