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.
32c04bbb9e981672a330a1ceb9f1f8455bba1609903f81b4d4ceadec50c78606
Both payments are on their chains and locked to the same secret hash a1062ade2882eecc46fc2162312a735a66011774, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 32c04bbb9e981672a330a1ceb9f1f8455bba1609903f81b4d4ceadec50c78606
- MakerPaymentSpent: 8530149bec00eb187e03390c695403fef0cf9ea0c478a5ff381c344858d8c067
3811c0e6f0e5c4eee92c66a0fc1c57a6820ea57ddc5fa46e551b4451f786d752
Both payments are on their chains and locked to the same secret hash a1062ade2882eecc46fc2162312a735a66011774, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 53d6af7d0843dad04c1c88ef787ac8571059cafb5187c02bad06ae6e83e34400
- TakerPaymentSent · TakerPaymentReceived: 3811c0e6f0e5c4eee92c66a0fc1c57a6820ea57ddc5fa46e551b4451f786d752
- TakerPaymentSpent: c32d0e9ed6310d8e587b446c439659b669e68ef6011073295a007880e939331d
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.