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.
fbc91cfdfcf51c257773156fb8ec4c890677158cbe717826367b5769dd022dcd
Both payments are on their chains and locked to the same secret hash e3c5e067e1516ea2d7650880f7f21590b10b41f3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · fbc91cfdfcf51c257773156fb8ec4c890677158cbe717826367b5769dd022dcd
570dd6f0cdf7799c0308b25182e707b6bb54c5d3396d18e7ebc3586a710fa2fa
Both payments are on their chains and locked to the same secret hash e3c5e067e1516ea2d7650880f7f21590b10b41f3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 4b81f39c173f3fa819ce5acf2f2e45ff7c98b1b3f493002d051220c0d4a74ee1
- TakerPaymentReceived · 570dd6f0cdf7799c0308b25182e707b6bb54c5d3396d18e7ebc3586a710fa2fa
- TakerPaymentSpent · 453b968d2c77710d9b5493f9a4b3a85e831c4a092f5f61c2493091cc84020911
No anomalies were recorded against this swap.
Reported by kdf-statsdb.