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.
22cfabe77f28f63f66085b7bf9800101ec14ba6446bcaec51b900351e2e48e2a
Both payments are on their chains and locked to the same secret hash 4398a5240ee120d7822041341df6eff395384d98, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 22cfabe77f28f63f66085b7bf9800101ec14ba6446bcaec51b900351e2e48e2a
- MakerPaymentSpent: db561bbca23f118300401130d0fff62c95df91aa58708299363d0e6b591a16ae
c5232ae1db2d2f37209f45a3260c2edfccf6edd33bb64f892dd84f209de28dbf
Both payments are on their chains and locked to the same secret hash 4398a5240ee120d7822041341df6eff395384d98, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 050965a050c9c16ac94c9f8f3b7722f1aba1b0b1798cb616e8f0d8f83a3de622
- TakerPaymentSent · TakerPaymentReceived: c5232ae1db2d2f37209f45a3260c2edfccf6edd33bb64f892dd84f209de28dbf
- TakerPaymentSpent: 201af8c56d8b0cd8d8caefb28ffb1f3d64647daae831883d5643a07f90e47b2f
Reported by kdf-statsdb-8762.