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.
6a1f3834ae798facb5be3457645897b7657d4468d1f53ecc6ad500f9d84eb8fd
Both payments are on their chains and locked to the same secret hash 4772e9d037f64f198d1544361de0d00aa1d7043d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6a1f3834ae798facb5be3457645897b7657d4468d1f53ecc6ad500f9d84eb8fd
- MakerPaymentSpent: 4ec306c4922a91fb5663f441beea6f658ecaa525574efc98df4010a3a3dab4ca
68b3345d5a945faa332248d89101faf3942a720852614b04beeba4c5336291d2
Both payments are on their chains and locked to the same secret hash 4772e9d037f64f198d1544361de0d00aa1d7043d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8985eef70e9660fb9b4c9d461e5ac9b473d144c28179649bb99f12e55f314b8a
- TakerPaymentSent · TakerPaymentReceived: 68b3345d5a945faa332248d89101faf3942a720852614b04beeba4c5336291d2
- TakerPaymentSpent: 6f6ab36486c1dd8e6d41d6bc3221dbf269508687150057b8ac7ac558b540c571
Reported by kdf-statsdb-8762.