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.
e253deb54ad7bdda1162adbe3237af8a2994f48e77064f62c129d23e07c403e4
Both payments are on their chains and locked to the same secret hash cb2f90d299b8e9207ba02464a4d2955f3c46703b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e253deb54ad7bdda1162adbe3237af8a2994f48e77064f62c129d23e07c403e4
- MakerPaymentSpent: d6808104a21325a8ee49107f6a0fa41e32264baed16497520bb42f9cf8912fff
84efe8b2a485653213ad5ddcd112912519f597cb476cd44884ced84ffc86d626
Both payments are on their chains and locked to the same secret hash cb2f90d299b8e9207ba02464a4d2955f3c46703b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f411ca520565fdebc4492dc8a039dc409ee91ef34e9c3b3b61a8eec63b48a90d
- TakerPaymentSent · TakerPaymentReceived: 84efe8b2a485653213ad5ddcd112912519f597cb476cd44884ced84ffc86d626
- TakerPaymentSpent: d77de1b70dbdafe9068f5999a6061f4434f21560ae42af3426efa86759b149ac
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.