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.
4fe8499b94be406b1776901e203cd5ce21e50aabdcc211f701cb4aaa6be614a0
Both payments are on their chains and locked to the same secret hash 1e5c8917d3955ad1552ba8105a99186f9b19dc79, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 4fe8499b94be406b1776901e203cd5ce21e50aabdcc211f701cb4aaa6be614a0
c1368dc727cd7ce47e73c98f7a78017b3f132471bc08a9c479291a2267129dc3
Both payments are on their chains and locked to the same secret hash 1e5c8917d3955ad1552ba8105a99186f9b19dc79, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 6f1b6cec46b1b4096a8cfa2d50e6e3944bc32cbd9cd6e9099c03e303cc88a5b0
- TakerPaymentReceived · c1368dc727cd7ce47e73c98f7a78017b3f132471bc08a9c479291a2267129dc3
- TakerPaymentSpent · 0eb9b100f7a481daef01bcb82ab7e720044af9a476f6324b651c08623d328bab
Reported by kdf-statsdb.