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.
1ad021e80d0c8f2f4f5d2c7e03d213b546e989f5d99f978f0e41dabaa7f0c3cf
Both payments are on their chains and locked to the same secret hash 5d446239859e18b54d1f8309cbaf0f460a0d9d2e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1ad021e80d0c8f2f4f5d2c7e03d213b546e989f5d99f978f0e41dabaa7f0c3cf
- MakerPaymentSpent: 0aa1de2573a399a9e21f9589985c2ccc059829edc1f069b377d502691905f6d2
9c67698679ee81269a53d3e11a194f52795dcebe79831605594b241ef22cfd58
Both payments are on their chains and locked to the same secret hash 5d446239859e18b54d1f8309cbaf0f460a0d9d2e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: eeb9c0ed894808feef8ce28d570082c745839f48d74c330b8d19fbd7da335a73
- TakerPaymentSent · TakerPaymentReceived: 9c67698679ee81269a53d3e11a194f52795dcebe79831605594b241ef22cfd58
- TakerPaymentSpent: 5f632382fd68c34e81ed747e9141e27ba63b1d763baf4118948568883011042e
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.