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.
e7d0ea7c04fb58fda3698ba18461c143a2c04b5ca876b3aed1f61cede3e94fe1
Both payments are on their chains and locked to the same secret hash d71b1f7313bd8ceeb53a0b8c970fb5b65b1d26b0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e7d0ea7c04fb58fda3698ba18461c143a2c04b5ca876b3aed1f61cede3e94fe1
- MakerPaymentSpent: 443c473968e8a7dea447ed3c4f79cd074582ab6f705755439de8836b04994d1c
d6a49c9577277b9e13f406b24f1fc97839c150c3564db39f203cb65f6b5f147e
Both payments are on their chains and locked to the same secret hash d71b1f7313bd8ceeb53a0b8c970fb5b65b1d26b0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3e371819b6b6d57c0834298b6292b1253774cea1c12fe22359ac78010be46ce9
- TakerPaymentSent · TakerPaymentReceived: d6a49c9577277b9e13f406b24f1fc97839c150c3564db39f203cb65f6b5f147e
- TakerPaymentSpent: 60d80e6b1393e2cda0d931166f4f4944b14d56dbc65a2a8bd3f2c60981475c20
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.