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.
24288792cf30619179ffa2953bbc28098bc5d62bb81f2c98912a76e767314940
Both payments are on their chains and locked to the same secret hash 986ad02d6c552826a908e02574a85bc11fb67b07, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 24288792cf30619179ffa2953bbc28098bc5d62bb81f2c98912a76e767314940
- MakerPaymentSpent: 771ed4972d360da532584da0095906806a207b519a905e1c46bc0188958c14a2
f4deab64fe4318fcfacd4f0156758288f51a8e2f7cf22b3f45c03a8a5369d06b
Both payments are on their chains and locked to the same secret hash 986ad02d6c552826a908e02574a85bc11fb67b07, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 855a13d282c64efcec3ea0bcded16561aae4d2c082500f05ff3da984317e22dd
- TakerPaymentSent · TakerPaymentReceived: f4deab64fe4318fcfacd4f0156758288f51a8e2f7cf22b3f45c03a8a5369d06b
- TakerPaymentSpent: c54a79feb18a3bf57370eb28a69e5423dc957f536f7faa60be6567123724c750
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.