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.
7a23003faca81eaffec2b1dea0fd998275812837917a05dc8827c0d749ee1572
Both payments are on their chains and locked to the same secret hash 0b36f3bb32a8a44e87057692c5c7306550a57b0a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7a23003faca81eaffec2b1dea0fd998275812837917a05dc8827c0d749ee1572
- MakerPaymentSpent: 14dca677bf85a155d108ef28c666c03143a605cba24d068e54f248f70a019ee9
38c2b273ef42c954da074dc77166ef1bffd166a8e96201c5ecf698fb6e1dd6f6
Both payments are on their chains and locked to the same secret hash 0b36f3bb32a8a44e87057692c5c7306550a57b0a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 7748bfe16c94d763b69b91a2114cd0d14df5daa79c4a3ceb3423406264d6d367
- TakerPaymentSent · TakerPaymentReceived: 38c2b273ef42c954da074dc77166ef1bffd166a8e96201c5ecf698fb6e1dd6f6
- TakerPaymentSpent: 172f2766e3054160112a5168f6085197de6ab50a1781257092b242f19b62e278
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.