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.
3e27dab11510fe1a3c5c0f6edbdfd86c1a67c089116f8ba3bc9a33c27da8a0ea
Both payments are on their chains and locked to the same secret hash 26ff173ca98530ffb67d4ce41bfb145dc7c1c9f1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3e27dab11510fe1a3c5c0f6edbdfd86c1a67c089116f8ba3bc9a33c27da8a0ea
- MakerPaymentSpent: d7291537f693118a615faf93362f77a01d8067eec59ed4e2336d5733487a25a3
bd3177e454cb52fae43115b6d57f49791aeddfe2d6ca24d3c8b9a302f0edd8c9
Both payments are on their chains and locked to the same secret hash 26ff173ca98530ffb67d4ce41bfb145dc7c1c9f1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0c9e3b0b14f8eb492ec015b036e255423ecf1cbb7105fc1466d401171b608a0f
- TakerPaymentSent · TakerPaymentReceived: bd3177e454cb52fae43115b6d57f49791aeddfe2d6ca24d3c8b9a302f0edd8c9
- TakerPaymentSpent: 0ece4b397727247201c7ec37feb4267f8bdb3eb9815373f5eb4ba15a5ebe319b
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.