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.
27a02c39e7e0b33c4e901a716029674fc6501403127bc86d87d4c126b389e84a
Both payments are on their chains and locked to the same secret hash 5d4e4205a7a8f3ee9c41a66c53bd9092be47d182, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 27a02c39e7e0b33c4e901a716029674fc6501403127bc86d87d4c126b389e84a
- MakerPaymentSpent: a36902304b545629f790120e86ab7ffd8be80b1453564c852658941b9ca2245c
affa584c14ccdebed47dbf4b855251e720989e5d5c70945de9c5df35545ae8e0
Both payments are on their chains and locked to the same secret hash 5d4e4205a7a8f3ee9c41a66c53bd9092be47d182, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6bf805d8f1e27350e87c7831f406bd88a119ea32421ab23146e2d6edd89c8e96
- TakerPaymentSent · TakerPaymentReceived: affa584c14ccdebed47dbf4b855251e720989e5d5c70945de9c5df35545ae8e0
- TakerPaymentSpent: ab5e5f7809b8ceaa983081c4b2373f18e3ea65821b1cf96cca981f5f35af97e9
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.