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.
0ac6282e86432eabf5ab29ca0cde4ebb3df9011b4cbeb2e1c757408270c2dfcb
Both payments are on their chains and locked to the same secret hash 6251fb672b2317d26e8ca20f7fed6544f00e48af, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0ac6282e86432eabf5ab29ca0cde4ebb3df9011b4cbeb2e1c757408270c2dfcb
- MakerPaymentSpent: 55b0a8e988d5e005d734667e2cca8d49fca212d59f1ec958d04b364290a8768a
7cf5885c91902c3973341c769d552a357bdb91b87daef0905356e6788d60c88b
Both payments are on their chains and locked to the same secret hash 6251fb672b2317d26e8ca20f7fed6544f00e48af, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a8e1251a26cc88bafd5a94d945729c26c88e8f1349396aee49762c1e1684a836
- TakerPaymentSent · TakerPaymentReceived: 7cf5885c91902c3973341c769d552a357bdb91b87daef0905356e6788d60c88b
- TakerPaymentSpent: 95bae5d694a8772342ed441c4048b4aee15017eda24953433ea89be93ce60f25
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.