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.
3f79d6aef97a4d82d8a810061f09b525d2abd210e187e93c94c88968975ebdeb
Both payments are on their chains and locked to the same secret hash 246519108fc9df3aa8b0e6eb8385a24f0c4158cd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3f79d6aef97a4d82d8a810061f09b525d2abd210e187e93c94c88968975ebdeb
- MakerPaymentSpent: 859c58b254a99c1b59d31cdfd8ed913b3b276f9c6af34fdc93552e3a7c676f4a
517bd301803ff93b18702b9e9817cffb970c977186261af0b4dd35bc4e7f5f0b
Both payments are on their chains and locked to the same secret hash 246519108fc9df3aa8b0e6eb8385a24f0c4158cd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 806cbd63d96d46ed4e1d2c64bdb6e2f415c1c919602cc2d35fcd7a0a9c4c01a8
- TakerPaymentSent · TakerPaymentReceived: 517bd301803ff93b18702b9e9817cffb970c977186261af0b4dd35bc4e7f5f0b
- TakerPaymentSpent: e39846fd42febeeaeb93da8b238f1f0f54c668908751d35593d92eb35156d482
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.