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.
c73c7c553711b111fae422bb4d676e19de342b9da80c76a7f8333197ce97ee0c
Both payments are on their chains and locked to the same secret hash 0d671e9a53f30b63ee9ee763f57487c36b2de14a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c73c7c553711b111fae422bb4d676e19de342b9da80c76a7f8333197ce97ee0c
- MakerPaymentSpent: 9730bf2a1999a55546cd82f4f4ceee5a7ee18f235ae43ebb178a4e8eacfac661
429432a869bdf0c42900d00037b784094314f0d8e19165294f8bd46f003e30de
Both payments are on their chains and locked to the same secret hash 0d671e9a53f30b63ee9ee763f57487c36b2de14a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6303a101d6a16015feb5b7e4459e758d3a583d7198a826ca40f78465f9251d39
- TakerPaymentSent · TakerPaymentReceived: 429432a869bdf0c42900d00037b784094314f0d8e19165294f8bd46f003e30de
- TakerPaymentSpent: 4975e72e006dab1f6549d6dac8398d7bd06ce1710c3b2262c413e750c9fb7a84
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.