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.
e26a1e2dac01f2f7e45640aa4cfc3865722af5ee5ed17f30d15db476b135382f
Both payments are on their chains and locked to the same secret hash e915b79fd812c071097b989395d5795a11067d53, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e26a1e2dac01f2f7e45640aa4cfc3865722af5ee5ed17f30d15db476b135382f
- MakerPaymentSpent: 1b51938286039084ab477a0341713f6fe842154bf06db5759639f4ed8d311822
2acfc8a3fabe025fc8cbbd3f7e3c302ec1aa22945589bc3127cc2eebba4da691
Both payments are on their chains and locked to the same secret hash e915b79fd812c071097b989395d5795a11067d53, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 492693dc143af9977edd31ebdc6e708ec57897f5e4b4c924617ed97342478f3d
- TakerPaymentReceived · TakerPaymentSent: 2acfc8a3fabe025fc8cbbd3f7e3c302ec1aa22945589bc3127cc2eebba4da691
- TakerPaymentSpent: cdd3d855ba30b37b342bd0cd3da29b4861f0cce0ec729112f2ba4b646cf7e650
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.