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.
d9b4a8575abbd7dbb16cc06a8de0b25eaac789cc6656a9fa320abfc262fc31d4
Both payments are on their chains and locked to the same secret hash 7eb12643737e8e16981316bbec1d76158ee2538b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d9b4a8575abbd7dbb16cc06a8de0b25eaac789cc6656a9fa320abfc262fc31d4
- MakerPaymentSpent: f6f2729f72fec43796d0f161bbd4bd9c394278b0288c8f3bcf8bd9d75697e7d7
ce355eada24a2d573b6157b4700a99ede5cc60290a32e898953508812cf4345d
Both payments are on their chains and locked to the same secret hash 7eb12643737e8e16981316bbec1d76158ee2538b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3d054a1723d569e4d3c80d3f4dd5d6a8a70db961a23abb62a7b4b9e964aef56b
- TakerPaymentSent · TakerPaymentReceived: ce355eada24a2d573b6157b4700a99ede5cc60290a32e898953508812cf4345d
- TakerPaymentSpent: 1b2ff0fd63a6703523c2b4db9b09ba48d6774da5f398617809396f516d74784f
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.