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.
1515d469fba27f0f8ff7ef3fed9373c881bd4f24d0c671fa428a5eb89b6d791c
Both payments are on their chains and locked to the same secret hash 1b7ecb8696dcd6c038eb2c3add97da919777ac01, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1515d469fba27f0f8ff7ef3fed9373c881bd4f24d0c671fa428a5eb89b6d791c
- MakerPaymentSpent: a240577a242c96c297a1f71f23316382864736ae559520ee6f643972c7d526cc
296a50f8b4dec8352a4194ef88734122faacb53ca7273f663581ed9deeffd0fd
Both payments are on their chains and locked to the same secret hash 1b7ecb8696dcd6c038eb2c3add97da919777ac01, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cda9569ac819abc73732ed71553b5f02d0cad0d4c1cfd15327acea45a089c0de
- TakerPaymentSent · TakerPaymentReceived: 296a50f8b4dec8352a4194ef88734122faacb53ca7273f663581ed9deeffd0fd
- TakerPaymentSpent: 4800797f0fa1988b32a67d3496f3e8eb0aaa55f00c9f2879ae8edb2e0d731202
Reported by kdf-statsdb.