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.
99c9aa9864cf4a1b51a196ac57bcc97e0d3115aab86abdaac5cadfb97df8892d
Both payments are on their chains and locked to the same secret hash 1ca24fd37daa68976e5fbe2bd72aa843ee0c4183, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 99c9aa9864cf4a1b51a196ac57bcc97e0d3115aab86abdaac5cadfb97df8892d
- MakerPaymentSpent: 0ad7ad6ca0e88ff0d132bcca18382fd82354fb8ef3c65666e4abb1a1c083821e
ddc55be53deabc8a9793de1a08e284529cd7551cb6804591c2fcd2fbd4b72794
Both payments are on their chains and locked to the same secret hash 1ca24fd37daa68976e5fbe2bd72aa843ee0c4183, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cf2fb63652214e8458a11c137127918a0119691ee2da7d171fb9575c369533db
- TakerPaymentSent · TakerPaymentReceived: ddc55be53deabc8a9793de1a08e284529cd7551cb6804591c2fcd2fbd4b72794
- TakerPaymentSpent: e4b1b8a2ea7b7eed1d8f1b3697537f7ae0189e828cd7b96c7d407a8dc0d78157
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.