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.
b3d8fa2b7a60c264186eb9e2456df46564c5629c78ad927721996f2f1f43de6c
Both payments are on their chains and locked to the same secret hash 81bc1e8ecd7629943c6fcf28e6e8d002094008a0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b3d8fa2b7a60c264186eb9e2456df46564c5629c78ad927721996f2f1f43de6c
- MakerPaymentSpent: a92af5039aad4b68fa42589cee5ee6a3edfbf47c424b1c3e5cdd134940aa46dd
af7d302c986902dcec44f7fa1bec6b1ab316e5ae89d214193f6c1f4ce8f529c3
Both payments are on their chains and locked to the same secret hash 81bc1e8ecd7629943c6fcf28e6e8d002094008a0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6696d919a8968e8335b517f87bfcbb72e7d523f1d59a0b0daf5ca9e9ce0b6711
- TakerPaymentSent · TakerPaymentReceived: af7d302c986902dcec44f7fa1bec6b1ab316e5ae89d214193f6c1f4ce8f529c3
- TakerPaymentSpent: ba51eb58bd6f0492f9f2c6a18aea35a7e503974455fd6b1fcc9bc6dbc94d350b
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.