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.
6eaf3af575655aad69c81b582e2d3ccb552dc800f50f964df100c2b9a55a5486
Both payments are on their chains and locked to the same secret hash d8f46f5d3d04b9e198a59c3918c4c79ea8270f0a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6eaf3af575655aad69c81b582e2d3ccb552dc800f50f964df100c2b9a55a5486
- MakerPaymentSpent: 0fc62f460361e659b8fde3e95724dbd73b38680d07019ad098b20bcad88dc4af
d9dbb2bcc368a088f02e4eeedff734af95e05d0eb03b079bfc0c42fc5c6eb6e8
Both payments are on their chains and locked to the same secret hash d8f46f5d3d04b9e198a59c3918c4c79ea8270f0a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e298226f64bed2b95a2a3477a221ee8ef1224399b44cb50bf557d1d4194c3ec4
- TakerPaymentSent · TakerPaymentReceived: d9dbb2bcc368a088f02e4eeedff734af95e05d0eb03b079bfc0c42fc5c6eb6e8
- TakerPaymentSpent: ec41dcd60c131936e94080a24d1fff734e30a419262f98665119e20f2ff29963
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 defistats-gleec.