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.
9579d6f3001dee63dec884175a29e01fee229d231b2efc51ca9f53bc52074926
Both payments are on their chains and locked to the same secret hash 9fac77218cc10ed540ad28a9c48ec299d99fcfd6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9579d6f3001dee63dec884175a29e01fee229d231b2efc51ca9f53bc52074926
- MakerPaymentSpent: 619ac6a6460b6e76e9071e636e4ff62e5aa4b0d00223db8b42cf452742ae2a6a
6a46544e5f4b8d38aabf51248af1fc721929563e12ac1031308ba4c2e8cc500d
Both payments are on their chains and locked to the same secret hash 9fac77218cc10ed540ad28a9c48ec299d99fcfd6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e33ee78feb4eec5f55f32103f93e3e5e814ca1bf96467f98747b0175fe62914f
- TakerPaymentReceived · TakerPaymentSent: 6a46544e5f4b8d38aabf51248af1fc721929563e12ac1031308ba4c2e8cc500d
- TakerPaymentSpent: bd36376629f150013e5fbf62f8b33edb3e82fbaaeb7d2e3539855cb6ee0663e9
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.