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.
9b06d88197465857eda9522d74386d05a436be560d9f324321fbfdbb8be3c2f0
Both payments are on their chains and locked to the same secret hash 6214379290ac883d054ced6a9a524f5480a43622, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9b06d88197465857eda9522d74386d05a436be560d9f324321fbfdbb8be3c2f0
- MakerPaymentSpent: 802f98b66a3f4fd6453b8b5aebba8e798b75711b72de5bc9063b5d30631d8969
7edc8865197aacfcde93ffecfe7075d939ef5d79c5f54ee9f2ffa3e20de2cb89
Both payments are on their chains and locked to the same secret hash 6214379290ac883d054ced6a9a524f5480a43622, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e81ecb5aa788688df0897ed4a4a01bbe976d2decde01cb7ca65fde6c755c67e6
- TakerPaymentSent · TakerPaymentReceived: 7edc8865197aacfcde93ffecfe7075d939ef5d79c5f54ee9f2ffa3e20de2cb89
- TakerPaymentSpent: 0dd4bf4c094b34a4d2b9d34c83b0b745faed538fe7100c721b30b1c27125e3fc
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.