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.
9231ef0fc88b63d7eb73acbf21bcb21eb59f5930e66526e164ad582f06f7315e
Both payments are on their chains and locked to the same secret hash 6ed2089560930845aa1c3e10f233a738da54f378, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9231ef0fc88b63d7eb73acbf21bcb21eb59f5930e66526e164ad582f06f7315e
- MakerPaymentSpent: 027cc8e6a60cdcfe859a21f7da5c4da40ee8f76af62c96f3c767a166834a0e64
14f3a4955948806d82958a68f23e7617dbc5f1754388028d2631a262d6ff4108
Both payments are on their chains and locked to the same secret hash 6ed2089560930845aa1c3e10f233a738da54f378, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e9fb2576832ffa46548fa4fb74d17284ce63b58740f9eef7b2fc2e851cde58a3
- TakerPaymentSent · TakerPaymentReceived: 14f3a4955948806d82958a68f23e7617dbc5f1754388028d2631a262d6ff4108
- TakerPaymentSpent: c08eb960b306275b15796b1d7a59857be2332103679bb07ab381baf50bb5a30a
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.