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.
d87310db923370e7493aecf025125ce7ddbfa27fa3eb1d2bd6bdbc248f3fb9d6
Both payments are on their chains and locked to the same secret hash c018d0c3172f366c2f909befb25dbaa5e21a18ca, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d87310db923370e7493aecf025125ce7ddbfa27fa3eb1d2bd6bdbc248f3fb9d6
- MakerPaymentSpent: aa04fb0bd3b686c9ef108ea92cb8b0a518db5fd8c41061b2bf34395488adc49a
0b88f4f23cda0a60b7d9e4655fa6390adb88cc3dff2a0a463ec085d30e8cd482
Both payments are on their chains and locked to the same secret hash c018d0c3172f366c2f909befb25dbaa5e21a18ca, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 121796beb5e1517e8eeb5c603b7cc8ef7b24b257d834d9e63ee86b03db90b2ca
- TakerPaymentSent · TakerPaymentReceived: 0b88f4f23cda0a60b7d9e4655fa6390adb88cc3dff2a0a463ec085d30e8cd482
- TakerPaymentSpent: 1cb379ee20b735134190bb68a759cec2e4d9ef732537925bbc9e1ae803ee34d6
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.