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.
4f13ff4d57934f2a5e42e6771515f5848ec85cf9bbc6ebef571121bc3a2a58f9
Both payments are on their chains and locked to the same secret hash 0800867ba076347a9f9d2380c9b9bb095544281f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 4f13ff4d57934f2a5e42e6771515f5848ec85cf9bbc6ebef571121bc3a2a58f9
- MakerPaymentSpent: 4f6722a8168dfcc5eef6f4356c3f117f84565d49f1898ab7ca3d200654137738
aaf2e75f654b605428cd7c50ebf8ad7d152bf1b0ba88e480acbbc5405d620d25
Both payments are on their chains and locked to the same secret hash 0800867ba076347a9f9d2380c9b9bb095544281f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9d3e8b545ba6a3986387b59a92dcaa543c7370fde1e379c00ea5fa8ea516ab67
- TakerPaymentSent · TakerPaymentReceived: aaf2e75f654b605428cd7c50ebf8ad7d152bf1b0ba88e480acbbc5405d620d25
- TakerPaymentSpent: d64b14f514945768ff32c2d49c797eea337482100486286312a729ec0922d344
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.