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.
9a5a41d4712eac2f0e44cb5e02acad7335625b1f5fdf9229c8f441ce87c67d3c
Both payments are on their chains and locked to the same secret hash af38d974f5ba4933ca5c40a17fd00069d2e273c2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9a5a41d4712eac2f0e44cb5e02acad7335625b1f5fdf9229c8f441ce87c67d3c
- MakerPaymentSpent: 26865c0c797a6c696d09fd40609bc21aae0d26f8efdec49dd13f9775db3e6a8a
c70df2b2a4c292744c87dac25fec00ee1e5ce83a44ff2e6c709370c3edc1ad46
Both payments are on their chains and locked to the same secret hash af38d974f5ba4933ca5c40a17fd00069d2e273c2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 779e15a2203402f3858f77d8535752287e697fde66949f8adf3449d6e26fbb1d
- TakerPaymentSent · TakerPaymentReceived: c70df2b2a4c292744c87dac25fec00ee1e5ce83a44ff2e6c709370c3edc1ad46
- TakerPaymentSpent: 2f4309f11bb5444673c9c841a9e0889588b3c82ee661fed15a3e25620e3d5b3b
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.