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.
b9a1fc02d1736299dea4569f4476fa5205ee5dc4375a30c68641f49c5507dc15
Both payments are on their chains and locked to the same secret hash c8a8373381dfccebf13760f3a268f380c8cad7fc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b9a1fc02d1736299dea4569f4476fa5205ee5dc4375a30c68641f49c5507dc15
- MakerPaymentSpent: 5080638a34a0e5801e865f0a81434b52446f7e33a53ceaa9c23ce8f8e5746f1b
1cfacf8290c61839ea9efcbf0abd45cbf3846be705e3b38b6522a577b0901279
Both payments are on their chains and locked to the same secret hash c8a8373381dfccebf13760f3a268f380c8cad7fc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 28f5450d8c8583abbbe0c0d8d2743e9bc1fc477bf0d71f0273df2020702c4d29
- TakerPaymentSent · TakerPaymentReceived: 1cfacf8290c61839ea9efcbf0abd45cbf3846be705e3b38b6522a577b0901279
- TakerPaymentSpent: a90c4c111fc06f5e9f258bc366bc3a44ddcec9fd7625af1f4044d2cae1dd13cb
Reported by kdf-statsdb.