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.
1b19d026197a7f270890f3fb6c78a5a8f7908a1ab95d09bb7be9b1c9a9c97cf2
Both payments are on their chains and locked to the same secret hash fe130a4904181799a26cfb7716fc1ccaf5c9cd73, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1b19d026197a7f270890f3fb6c78a5a8f7908a1ab95d09bb7be9b1c9a9c97cf2
- MakerPaymentSpent: ef218c277a28585c7e6a72e419b256feaddb7df2de13de2e0063e2843ba18973
cf7ec4677ca495e768bf96d7743a7abe767a89ff624be839ca51f890109c7488
Both payments are on their chains and locked to the same secret hash fe130a4904181799a26cfb7716fc1ccaf5c9cd73, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 86402813b46758e5dd6170137e877633da848f995b50137feadd9fc83d6f77cf
- TakerPaymentSent · TakerPaymentReceived: cf7ec4677ca495e768bf96d7743a7abe767a89ff624be839ca51f890109c7488
- TakerPaymentSpent: 676b659bbdf70f54e3e800bc7d98118ed57b088ac61cd72a0d04913b4ac66038
Reported by kdf-statsdb-8762.