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.
62b00307c5216e392d4c84f5e8668eeafef671a76e49a8502e61b18295802da9
Both payments are on their chains and locked to the same secret hash 2e380d2c753b809dfde0ba34a4d70f507ea1830e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 62b00307c5216e392d4c84f5e8668eeafef671a76e49a8502e61b18295802da9
- MakerPaymentSpent: d6e62e4542f6f3f90eafe966fd7dbf58c3eabb9c9d95c78b6ea40937875a7077
193705c8726bcd9cc668c0cd20fb76b7f05a765954b0e7de541b63b0422e2a49
Both payments are on their chains and locked to the same secret hash 2e380d2c753b809dfde0ba34a4d70f507ea1830e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 12acb518960cf8f395d8d64def250d2549ad9ee761649e155dc34f44d5313d8e
- TakerPaymentSent · TakerPaymentReceived: 193705c8726bcd9cc668c0cd20fb76b7f05a765954b0e7de541b63b0422e2a49
- TakerPaymentSpent: fcaf0d7ffb7e8df66dbba6787d7f8e4bb5e7e5ad185f25f938df7665af6920fa
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.