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.
fe463d01daad2d5a22f10408a3396b2e731ae7de4e8e9bb4de802fe64cdd7041
Both payments are on their chains and locked to the same secret hash 67b6c8abf9d6f003022dd4bac0964bd098ed4e44, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fe463d01daad2d5a22f10408a3396b2e731ae7de4e8e9bb4de802fe64cdd7041
- MakerPaymentSpent: 58179e9419d548ca61ff92348be51e4d7976fc68e4d2a715d0a3cd53909c2eeb
a64923322dad96ad449167a1b5918c27cd499468a6318514c979c6906265e092
Both payments are on their chains and locked to the same secret hash 67b6c8abf9d6f003022dd4bac0964bd098ed4e44, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9c10bf28e0ef8cdd566dd661f4737305654d58dfe1f8024a2f0d9f25a8e5ddfb
- TakerPaymentSent · TakerPaymentReceived: a64923322dad96ad449167a1b5918c27cd499468a6318514c979c6906265e092
- TakerPaymentSpent: 0c511127121034fdf0222ba2d842370e8fbf6069372fe2c07f14510371cd6cb3
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.