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.
1645738f9811749f0de198793619534427ee614936d4a30980b5372d91f09958
Both payments are on their chains and locked to the same secret hash ff63645c3bb3b67c8c59256bd65eca3828174d6b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 1645738f9811749f0de198793619534427ee614936d4a30980b5372d91f09958
7ee85503516cb48aab18838ca3ba17306991bb817d119d57c52703bd038c609f
Both payments are on their chains and locked to the same secret hash ff63645c3bb3b67c8c59256bd65eca3828174d6b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 58be1007c03722cfc8b529d8ba3048413aa543a441806d0d4d31e79c1af53fb6
- TakerPaymentReceived · 7ee85503516cb48aab18838ca3ba17306991bb817d119d57c52703bd038c609f
- TakerPaymentSpent · ef4d88750c7ad53cfd254ecab614e2818c60628e9b2fe445e891cb1c14c1af70
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.