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.
867df61f79dae93afdc8fb14feb27bda8815dbb7cbc447f819afd5f98c02b208
Both payments are on their chains and locked to the same secret hash 5766db11bd3df1618a5d24e9e5a942ed4e97e0fe, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 867df61f79dae93afdc8fb14feb27bda8815dbb7cbc447f819afd5f98c02b208
- MakerPaymentSpent: 7904ad34391e306a84cf141a835d6dd5b194783de2c41de19419d18c069b7721
cf8fa4577e9768ea7de1c325aeb94a8626502e6844e25f7f81c04d94148b72c8
Both payments are on their chains and locked to the same secret hash 5766db11bd3df1618a5d24e9e5a942ed4e97e0fe, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e5970d167d1f7d1a63ea64dfebab8b100e32785aa597f3f8c379db24a52dfe8d
- TakerPaymentSent · TakerPaymentReceived: cf8fa4577e9768ea7de1c325aeb94a8626502e6844e25f7f81c04d94148b72c8
- TakerPaymentSpent: e7b1639c35e63f10dd4e3f7554d8f8cf74c5457f77585045adfd0f1cac3295e0
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.