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.
90e4f535c82e4ff9ffe1259c0fe03ea4c833259434e2e1a4fd1be42b87ce4612
Both payments are on their chains and locked to the same secret hash c39b618d6194a5b519a7fa74d29abb6184603c62, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 90e4f535c82e4ff9ffe1259c0fe03ea4c833259434e2e1a4fd1be42b87ce4612
690c765efd447f96bd49b781f6d83ed68f1d3bb6d49cfe97145d681d11065bb8
Both payments are on their chains and locked to the same secret hash c39b618d6194a5b519a7fa74d29abb6184603c62, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · d5d5c25a2127fa494f7985fdbc6dd808abf8e301849a88fc2b4e5d20ae66831c
- TakerPaymentReceived · 690c765efd447f96bd49b781f6d83ed68f1d3bb6d49cfe97145d681d11065bb8
- TakerPaymentSpent · fd0884b54570c7af1e0ec0a0ad3515d035f1d495801dce7e13bb79a4c8ced9d0
Reported by kdf-statsdb.