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.
07eb18687497da4c743e4e65169ba661ae55515c0331089c64dff17811a883cd
Both payments are on their chains and locked to the same secret hash e6c6c37162ecf95d3104b41f15aa074074ea4db6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 07eb18687497da4c743e4e65169ba661ae55515c0331089c64dff17811a883cd
- MakerPaymentSpent: d15b7512bcc59a5ce49acbbfb040e41c9c046c251104d66ffcfa1e80b8ad027e
bb50272ba3d1db082dfaa2126f4469e57891a4424d6921bdd0389cd78e1bd174
Both payments are on their chains and locked to the same secret hash e6c6c37162ecf95d3104b41f15aa074074ea4db6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 58a83779519ada7c05b405687c25ab820fd8300d4056f3df4b11d1fe45fc0244
- TakerPaymentSent · TakerPaymentReceived: bb50272ba3d1db082dfaa2126f4469e57891a4424d6921bdd0389cd78e1bd174
- TakerPaymentSpent: 41173b6b64dd0a7121b3ef0d6f2702171fc16d8506633c78dae75eeb0f7095d5
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.