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.
e923a61f965ff21c083f3a6b856dce0844b5fa2ade4429da97991a9863fa6a83
Both payments are on their chains and locked to the same secret hash 89ea667da196971ef057a5b4fc2e8562fba61639, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e923a61f965ff21c083f3a6b856dce0844b5fa2ade4429da97991a9863fa6a83
- MakerPaymentSpent: 627586ab8d87c64284c35edc6546dd46dda053431a8483f04913b56c8f27dd70
d6c114a2b63915138585a50619ab1877b0db27d8ff2eff1ed842b9456a0ebbac
Both payments are on their chains and locked to the same secret hash 89ea667da196971ef057a5b4fc2e8562fba61639, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 27b3f364f40508032ae289991e71ca7f84487c20eaf002fbe017a4a4bbf23f80
- TakerPaymentSent · TakerPaymentReceived: d6c114a2b63915138585a50619ab1877b0db27d8ff2eff1ed842b9456a0ebbac
- TakerPaymentSpent: 81c972ab3319a537157e6a1f98329e5b554fbcd7db72b9165d76b905bb3401c2
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.