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.
c082cea368f023c8bbff9ad1466b6c46d5c323047de4a21704376a17c0cc90de
Both payments are on their chains and locked to the same secret hash 8f7f94740b4a85285740ccf6760d27506d269411, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c082cea368f023c8bbff9ad1466b6c46d5c323047de4a21704376a17c0cc90de
- MakerPaymentSpent: efbf25c06fbaac7b72dd676b44716d69ef600cdbb8229ddea04382e41a93f99d
add9538bacc19f24b29007cb2501a00e9d8261cf6ce25fa24471bf6a1acf9cd5
Both payments are on their chains and locked to the same secret hash 8f7f94740b4a85285740ccf6760d27506d269411, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e5ea8d681364179b9e812754a7b3b634dc127ee090d7c40bce090fe9985939a7
- TakerPaymentSent · TakerPaymentReceived: add9538bacc19f24b29007cb2501a00e9d8261cf6ce25fa24471bf6a1acf9cd5
- TakerPaymentSpent: d6221a8840ea723e740c72776071710886fc6ab9da32f0acae6ddb983c3dc968
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.