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.
8283101ec4d56bd7c2173a1fc3ba5da63f02744660058576f1b11154329a4a8f
Both payments are on their chains and locked to the same secret hash f3570038751ec530c01a58873db9015f956a4d5b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8283101ec4d56bd7c2173a1fc3ba5da63f02744660058576f1b11154329a4a8f
- MakerPaymentSpent: ccbf6d38e20547d8eeded75e156881fbebdcd85bae5c9bb0af9ff6bf1cfbdf2b
5dc4a0cab5605e55fe477c2b92719ac5a54c770efbf4432f7a564939d80fb656
Both payments are on their chains and locked to the same secret hash f3570038751ec530c01a58873db9015f956a4d5b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b56dbbdae721780c658057f4436d778781fdf2089bb96dbd7e28da063a747c8e
- TakerPaymentSent · TakerPaymentReceived: 5dc4a0cab5605e55fe477c2b92719ac5a54c770efbf4432f7a564939d80fb656
- TakerPaymentSpent: f573fc5c1b81b2e9e76e84f4f50280ed5663de5404f38808fd7a07ed88919e66
Reported by kdf-statsdb.