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.
f8cee997783486de1256c6bf580dc895f79a7a2659be6556843ef1a70714d142
Both payments are on their chains and locked to the same secret hash 632c3f41581a40b65427e180c8af4019ff4d66ce, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f8cee997783486de1256c6bf580dc895f79a7a2659be6556843ef1a70714d142
- MakerPaymentSpent: 84737671461e529e7e59d9b12e11eb994938cff5d711e5fae60500afd75916f9
9514d1be88d64eaabf3c128144e5b0f5195dfde7e2090b739f6f291eebead1d3
Both payments are on their chains and locked to the same secret hash 632c3f41581a40b65427e180c8af4019ff4d66ce, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 55083ade0c6ee10b9c17fa8814922d5a46d209ffecf28c19534bd1792a60726f
- TakerPaymentSent · TakerPaymentReceived: 9514d1be88d64eaabf3c128144e5b0f5195dfde7e2090b739f6f291eebead1d3
- TakerPaymentSpent: 821859742cd4d27ce338ccbb29a3054125f9b62ed0f7eaf6e4249f943e44f18c
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.