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.
8c5a7b699887f15fa13d5dfd8844541c92452e7470dcd5c051a65956e58cd282
Both payments are on their chains and locked to the same secret hash 6ce47c73ee6adebf5cf8f0d5baf7258f36fa7dc3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8c5a7b699887f15fa13d5dfd8844541c92452e7470dcd5c051a65956e58cd282
- MakerPaymentSpent: 0a1cf26b527894d8cc30f805b5b20526af34fb21e12af8be173c2dfe452e3687
f68d884bc30bf3bbe0a290a5f79ab3dce409f25cebe72049df8bb8163b13f904
Both payments are on their chains and locked to the same secret hash 6ce47c73ee6adebf5cf8f0d5baf7258f36fa7dc3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a867a1eb329fa4bd22ed43c9a46d827625785b838351cea54701cda765a2a835
- TakerPaymentReceived · TakerPaymentSent: f68d884bc30bf3bbe0a290a5f79ab3dce409f25cebe72049df8bb8163b13f904
- TakerPaymentSpent: b2528be079fad7678e000dba7259b26e5234844775199d2fd560ee9a6c361c63
Reported by kdf-statsdb.