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.
105ca2f35fe84b7d52bab7c28278bfed06472d584b313dcdc6e56cf11063785a
Both payments are on their chains and locked to the same secret hash 19da0dab5b8735040f78cce4662aa11ff71b437e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 105ca2f35fe84b7d52bab7c28278bfed06472d584b313dcdc6e56cf11063785a
- MakerPaymentSpent: 3c4918d2e14ddaf87f9b133112e20f5b65b162e9440d52068c566af3f8d6bdeb
55892cf2eca76ba625100f6a8dc7034bf699963fcb46d6d1991ca8a99c78ba16
Both payments are on their chains and locked to the same secret hash 19da0dab5b8735040f78cce4662aa11ff71b437e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e1ae5e5a75796af09c8620b06b08305c2c2e5a423bf507f3bd5eab0a1ed7e84d
- TakerPaymentSent · TakerPaymentReceived: 55892cf2eca76ba625100f6a8dc7034bf699963fcb46d6d1991ca8a99c78ba16
- TakerPaymentSpent: aee3362fcf331cc4e83ec48c88ea8dc3e065bca31e728da464abeec0494e1d56
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.