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.
4f7b4c0a1fb28e33cf1069426246cad1a77f75425845c95365780d52b34dca80
Both payments are on their chains and locked to the same secret hash 55b2e4e39ae7c78a4ddf1036858e6289e83372cf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4f7b4c0a1fb28e33cf1069426246cad1a77f75425845c95365780d52b34dca80
- MakerPaymentSpent: 7deb941b7a800002ad2726117f2fea35c45d97944c0f938e1efb477a166f59ca
a44f1980f7d8a8c4a9ce24f004e216c4b20c1039c560eae6d1ba055ab4340682
Both payments are on their chains and locked to the same secret hash 55b2e4e39ae7c78a4ddf1036858e6289e83372cf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1eecc25fb1afdd3dd9128e970766ef78872fdd003343cefd9c12983083e6bb32
- TakerPaymentSent · TakerPaymentReceived: a44f1980f7d8a8c4a9ce24f004e216c4b20c1039c560eae6d1ba055ab4340682
- TakerPaymentSpent: 60adbf8369addab568b62cf577eb0a2e9e32448fcf9feb4005007c66cb3cbb9f
Reported by kdf-statsdb.