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.
5e6c05692f5519943d9af7bb9d3086e66027e8e2164f0190263842c13810b28b
Both payments are on their chains and locked to the same secret hash 047c0e231f0ade6e79d3e72de17bc951a99a2af8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 5e6c05692f5519943d9af7bb9d3086e66027e8e2164f0190263842c13810b28b
- MakerPaymentSpent: d93cff02f5fdc1eba0a2320030393ed25219b38bac9b16f9f1daeab0eb290dde
c3b514ead8a6f51799f7dc499dbca16f9fab604fe9006e806d6b2e09a1c05044
Both payments are on their chains and locked to the same secret hash 047c0e231f0ade6e79d3e72de17bc951a99a2af8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 94239ff4a3a2c5572e3df6bf9680b1dc0bae6fffd918121ef07749f936262111
- TakerPaymentSent · TakerPaymentReceived: c3b514ead8a6f51799f7dc499dbca16f9fab604fe9006e806d6b2e09a1c05044
- TakerPaymentSpent: d9ae2ed24ec5582003dbf63db7ad782ae9a1aad0b6b967bf35c0134050b75ddb
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.