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.
446865c551faff7d8f8db60218e3884caaf5966bad4e9fd4e268abe1ffb22095
Both payments are on their chains and locked to the same secret hash 61ec66693858920d6593ff48850c34379b57bfae, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 446865c551faff7d8f8db60218e3884caaf5966bad4e9fd4e268abe1ffb22095
- MakerPaymentSpent: 29a417741d4249a1a2926f90a32b568ef7edc75190340cbdccde89bc22088be6
f8a64498229486007baa5b5535bbbdf31d98ff2fe46406e3ae06d9468e9018df
Both payments are on their chains and locked to the same secret hash 61ec66693858920d6593ff48850c34379b57bfae, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 764648e1a8e2055337a3ee58fa2ddcb04d3561739650d486059319ae9b5673a6
- TakerPaymentSent · TakerPaymentReceived: f8a64498229486007baa5b5535bbbdf31d98ff2fe46406e3ae06d9468e9018df
- TakerPaymentSpent: a35614a1274d5f566d5b7f833d1c3445006c2217040211acb0c0fdf12b0bd4d5
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.