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.
d5783d6bb2d9f6fe9b031b88ea95274183624b76014135c3155c6ca85e8d4915
Both payments are on their chains and locked to the same secret hash 066e64b3ac7926899101ce23e0ca459f2c747e84, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d5783d6bb2d9f6fe9b031b88ea95274183624b76014135c3155c6ca85e8d4915
- MakerPaymentSpent: 007e0c982b5b7951ea36fb759c97eabdd4fd134a3ec2fc5b4a401785b78516be
0ed77d9e2adaa4dcda4067e464901956ca5068885de7d98751fa69109167703a
Both payments are on their chains and locked to the same secret hash 066e64b3ac7926899101ce23e0ca459f2c747e84, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 22f9ec58d7dbae3d7322528e8376175915e6145d148d7a8e13dcdc8a5c40d75e
- TakerPaymentSent · TakerPaymentReceived: 0ed77d9e2adaa4dcda4067e464901956ca5068885de7d98751fa69109167703a
- TakerPaymentSpent: 28319fe0a11bf2570455b613729841729eb934d4c8ef1f9e54c276edbb87e526
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.