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.
0e85e943a18fab3c1a367e3dc8dd771e4361ddec0a3f982ec092c46a297b3bed
Both payments are on their chains and locked to the same secret hash c80ca8426278b226083d56e1c726dd89f78a62a2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0e85e943a18fab3c1a367e3dc8dd771e4361ddec0a3f982ec092c46a297b3bed
- MakerPaymentSpent: 3377116afddedc7429b85b3a33bd295b65bea8639f683564235fb164c98280e7
d076213904710f3ecf3ecfa5808fd62a7b3dde0d03ad9d64587628209148d2b5
Both payments are on their chains and locked to the same secret hash c80ca8426278b226083d56e1c726dd89f78a62a2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8227a02abd6ea19d21bb347796ae20c490573c32e2381107bdb4d48591817d14
- TakerPaymentSent · TakerPaymentReceived: d076213904710f3ecf3ecfa5808fd62a7b3dde0d03ad9d64587628209148d2b5
- TakerPaymentSpent: d203d03ffbc9a9c329c03c42efb03088df9f8273d49163577ba4899ed83c0246
Reported by kdf-statsdb.