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.
3f191e49cf2147ed17859f6ad421e5eb602d2633f28884af8bde0632e87db67d
Both payments are on their chains and locked to the same secret hash fda2659542ee43d393ead1645b6a8855d7dc6cca, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3f191e49cf2147ed17859f6ad421e5eb602d2633f28884af8bde0632e87db67d
- MakerPaymentSpent: 2227587a975145fc1cdbcc4b6f544e75de67331ff1a36d270cf6d83fbf24e148
e55d436437c37ebb4f35577d9abe82ae86def19ba3e5f863e720a68a7ed4501a
Both payments are on their chains and locked to the same secret hash fda2659542ee43d393ead1645b6a8855d7dc6cca, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: a0c20d4a6e9f63610f6f97cba5cb9950db3df28f3d996190ed90a369fa89bce6
- TakerPaymentReceived · TakerPaymentSent: e55d436437c37ebb4f35577d9abe82ae86def19ba3e5f863e720a68a7ed4501a
- TakerPaymentSpent: 8b5fafffe3acfe3c2d152a720b7454e53bfcdea45b2ba944ea68434996df3ba4
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.