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.
a6279cd073d4d4264203f4b14273f48420642aaef4ff0d38a2a8efd567d0f782
Both payments are on their chains and locked to the same secret hash 6eedff00b5fa8e772f805b92eca2c17fd32fbdcf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a6279cd073d4d4264203f4b14273f48420642aaef4ff0d38a2a8efd567d0f782
- MakerPaymentSpent: f08c0f0b75798eab6a4b758c511409446626d5155ce52962e103d59a5e4dcd43
1b4150cc72db747734f60f07ea702f48999205df27e354f271d9fcc638ec9f5d
Both payments are on their chains and locked to the same secret hash 6eedff00b5fa8e772f805b92eca2c17fd32fbdcf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 23eee3ef5d88320a1797d3053b61e3b36e29f27a40ebd079f5fb3777311dfff2
- TakerPaymentSent · TakerPaymentReceived: 1b4150cc72db747734f60f07ea702f48999205df27e354f271d9fcc638ec9f5d
- TakerPaymentSpent: ac56631510852588a20468542e4857c3b884b207738a71156402f700ff2d042d
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.