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.
ce323bcedddd5083f8c9a0ca877468e96532064f59bda8057ef268626e7931be
Both payments are on their chains and locked to the same secret hash f164279422cacd1a40f89bb5cc22ab97248fe629, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ce323bcedddd5083f8c9a0ca877468e96532064f59bda8057ef268626e7931be
- MakerPaymentSpent: da5afdd6047b5765790a554e26874416ab84af16233619f490ca5673d156621e
64f42325897314e65a81717d2d0bf36e4a03f3126dfb0659d772b38755f847c3
Both payments are on their chains and locked to the same secret hash f164279422cacd1a40f89bb5cc22ab97248fe629, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 731b62e3fc805529bef61837ae7db16dc7dd81b2f7fa1eb52313d321e9dab6fb
- TakerPaymentSent · TakerPaymentReceived: 64f42325897314e65a81717d2d0bf36e4a03f3126dfb0659d772b38755f847c3
- TakerPaymentSpent: ef9e1da63f857d0cb14c5721d6030ef5e73b425289bd9662c04297eda9d67edd
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.