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.
97e3e2b71ac769320b9ddb073287ce213044bed5131ae5170c90dafb318dedbd
Both payments are on their chains and locked to the same secret hash e2bba733e6eea862ada46301cf0e60089f3c8eaa, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 97e3e2b71ac769320b9ddb073287ce213044bed5131ae5170c90dafb318dedbd
ba743b278a28090bbf2c56868d2bcdd23d0504630ff5ddcb8055a0141fe53cad
Both payments are on their chains and locked to the same secret hash e2bba733e6eea862ada46301cf0e60089f3c8eaa, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · c5a0affeac2e7d060e4e5da5aae64be5c114708e4a43bbd5ff9736391468479f
- TakerPaymentReceived · ba743b278a28090bbf2c56868d2bcdd23d0504630ff5ddcb8055a0141fe53cad
- TakerPaymentSpent · 7840b26468c1aaf606bf4ed320d5c016f58eec2f88ba268519bad45d10777d4a
No anomalies were recorded against this swap.
Reported by kdf-statsdb.