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.
5a0aba0de2da903cb6a4d0b26cf2ca99283781c1ebdaf5c3c8ee4300a3dcd8d1
Both payments are on their chains and locked to the same secret hash 8c2b218646eea9527caa104afe7896634d9acd97, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5a0aba0de2da903cb6a4d0b26cf2ca99283781c1ebdaf5c3c8ee4300a3dcd8d1
- MakerPaymentSpent: a27432548583a4dbdeaafb04a1d7311802eb7ee7161b12657e37f1cc41dad1c0
35f662d328f2fde587b98abd3c1fe5ed0041dc8550f21eb24f7a01d81135deb7
Both payments are on their chains and locked to the same secret hash 8c2b218646eea9527caa104afe7896634d9acd97, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 71f138d6af15f1a8f12d57723020ecfbb6d897dfbb7bf7f0c0110e354b9dc84a
- TakerPaymentReceived · TakerPaymentSent: 35f662d328f2fde587b98abd3c1fe5ed0041dc8550f21eb24f7a01d81135deb7
- TakerPaymentSpent: c20cab4c1c653892e7766253fa352c89562628d91bce0467ef32ad72b52eaad7
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.