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.
8735ee9259547ba07c23a3dd80ed374e1859582e85a5a9ac86a4baa83451df2e
Both payments are on their chains and locked to the same secret hash 682203073b6121bf8cb58605236b79cc01c6fc29, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8735ee9259547ba07c23a3dd80ed374e1859582e85a5a9ac86a4baa83451df2e
- MakerPaymentSpent: 2dc97a108746b63703d5592243c4eac43b9f6f3bad85773bd6513e14ce03a7ab
a1ce5c0df2abbd99d28b0d2310790255a283c4ac8a6adab371b507bc8e05f944
Both payments are on their chains and locked to the same secret hash 682203073b6121bf8cb58605236b79cc01c6fc29, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dc4176b3a937fdae72250522df63dbe77d243e2f1b9b0fa0de626747082af8cd
- TakerPaymentSent · TakerPaymentReceived: a1ce5c0df2abbd99d28b0d2310790255a283c4ac8a6adab371b507bc8e05f944
- TakerPaymentSpent: 6dfafd2b706bc4606b4e62937615fccc1af686535355636e868a4c46b0554e4a
Reported by kdf-statsdb.