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.
20251f15df89f1924f991eaa1481083844317ff8c16b45d91a6a6d3ce218c758
Both payments are on their chains and locked to the same secret hash 2458e427b5bce9111e8ac028703dca1e9ae96536, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 20251f15df89f1924f991eaa1481083844317ff8c16b45d91a6a6d3ce218c758
- MakerPaymentSpent: 7ed918fb93e6b0e942ba5cd951c5db6e09f26c4bee13b716f630256162a2eec2
a327d640bcb5e5eeee4166e1665a3e31a339b89df6740452b6cf7c586a925ff6
Both payments are on their chains and locked to the same secret hash 2458e427b5bce9111e8ac028703dca1e9ae96536, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 86bc77d2bf2ef427d7b2a2eb0d47f63f3d88555f41350cb9a0c60710ec8b1008
- TakerPaymentSent · TakerPaymentReceived: a327d640bcb5e5eeee4166e1665a3e31a339b89df6740452b6cf7c586a925ff6
- TakerPaymentSpent: e21b6a8660ae39d5d8ac052695bd132f6b89c9df63c6cd0491ba0347cbd5a8be
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.