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.
17e0c717de40e9c838fccde87e428688dbd09d8cdccca162ece0403ca76b948f
Both payments are on their chains and locked to the same secret hash 366380c32bdc20aff5ae4557ef7bc54fb582a4b7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 17e0c717de40e9c838fccde87e428688dbd09d8cdccca162ece0403ca76b948f
- MakerPaymentSpent: bb3366a7723d8935d3be67d6a79818d3b9a9fad30d63c845872bb3f47f3e159b
810e59527b48f9577daa605e709c7304ef9d1f241b16a21413fd608eb25893ac
Both payments are on their chains and locked to the same secret hash 366380c32bdc20aff5ae4557ef7bc54fb582a4b7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 2f0f92a0c37ebab2fd13ece7f2c5ee843e72516f2f26a30d92cb8004a525d0d2
- TakerPaymentSent · TakerPaymentReceived: 810e59527b48f9577daa605e709c7304ef9d1f241b16a21413fd608eb25893ac
- TakerPaymentSpent: 297f62b3efd6e8bc8a37f9b06c1491d48fe2d61d8ae1138607a1d48365187ce5
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.