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.
874252d33ac6f706e98d58c8b259a96c402cdaaab9dc18dbed588ab3065f1e0e
Both payments are on their chains and locked to the same secret hash a9a5111ad63948d9d11c1fc0a062cd8f1fd663de, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 874252d33ac6f706e98d58c8b259a96c402cdaaab9dc18dbed588ab3065f1e0e
- MakerPaymentSpent: b9fcf3b851a9438e4f5dc9b6918ee616063ac811a53c739a391a67a682ef7cb1
dd0330fbf4bcd0874320697444545c85a1d02fdf1cea1c69c2bd751d9546846a
Both payments are on their chains and locked to the same secret hash a9a5111ad63948d9d11c1fc0a062cd8f1fd663de, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 50f2d70c8c267f1e171c836bc2bd26aeed5b8712f81ee15f59c244b36bb89562
- TakerPaymentSent · TakerPaymentReceived: dd0330fbf4bcd0874320697444545c85a1d02fdf1cea1c69c2bd751d9546846a
- TakerPaymentSpent: 480dff26e7c721cb0ce55b4b21a221ddf67e98779c9dc8c4bae141bff2fc1eb4
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.