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.
d69f982a0c774244f81480018738467850738529945cf20456c6de7bcf2af4f6
Both payments are on their chains and locked to the same secret hash 7b9712b4742e1ca1f0d63603fa6ab6208e491a01, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d69f982a0c774244f81480018738467850738529945cf20456c6de7bcf2af4f6
- MakerPaymentSpent: 692434748812803c9118184bfb571b5c56cfba92ce997792d154797f328be2a9
fdaa84e5256719afe0705a25a971794a32fc0acd0fa65d271e182d1acc89a3dd
Both payments are on their chains and locked to the same secret hash 7b9712b4742e1ca1f0d63603fa6ab6208e491a01, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a7892e23cff96240380dfc6af3f250961b047acb2ec1e246a90c14866ea00967
- TakerPaymentSent · TakerPaymentReceived: fdaa84e5256719afe0705a25a971794a32fc0acd0fa65d271e182d1acc89a3dd
- TakerPaymentSpent: 62ea9997e50fa49851e8b3be26dde2a48b8826539c6904737cc613088a32593c
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.