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.
53ffe8d0c12c3c5ecf5e49f1a2c41da2576c1f2c8fabf28a6936d712d8aa0243
Both payments are on their chains and locked to the same secret hash b4aca369dbfe2acb5b2b082570e70c1907d5e440, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 53ffe8d0c12c3c5ecf5e49f1a2c41da2576c1f2c8fabf28a6936d712d8aa0243
- MakerPaymentSpent: 540be2705be1acaaea1a01701a8be4bf692ba714f89be9d3481a0e39d5b190f1
6ff3e1ca652331eb8ffb4a40bcfff861a1eee2809938d8403b79365c5cde4cb5
Both payments are on their chains and locked to the same secret hash b4aca369dbfe2acb5b2b082570e70c1907d5e440, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a0764eb121e74b2e7a95442fa74b5f8d07844657efb066a751c45dce4a406088
- TakerPaymentReceived · TakerPaymentSent: 6ff3e1ca652331eb8ffb4a40bcfff861a1eee2809938d8403b79365c5cde4cb5
- TakerPaymentSpent: 9587d7bea15ce4ad04e34cf5c83ea5c52577adcd08c05402f9acb20c1fab24aa
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.