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.
1a664fbd4f34909485674e5c5cce6685dff50341ac1f920604002d54b92cdbb1
Both payments are on their chains and locked to the same secret hash 237f6a0d339930ee95259b0b8a18174bb27c5843, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1a664fbd4f34909485674e5c5cce6685dff50341ac1f920604002d54b92cdbb1
- MakerPaymentSpent: f499b515ff51c4d20efe8b050cabd4465427f380fa3083cc88d5a188514f513c
7bca28e1ceff911e09a08b478c757cdca1b91d480601f7ccd39e7342847060c7
Both payments are on their chains and locked to the same secret hash 237f6a0d339930ee95259b0b8a18174bb27c5843, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 98d273a5106cdecbffaf8074366df72546f0f414daf25fd849efab8549a709d1
- TakerPaymentSent · TakerPaymentReceived: 7bca28e1ceff911e09a08b478c757cdca1b91d480601f7ccd39e7342847060c7
- TakerPaymentSpent: f7aaf2ca6276ac9c1f0b796ba52839788740df08f17f67bf7bc8327e01b8279e
Reported by kdf-statsdb-8762.