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.
18c0777a39cbae477638c9165157d0fc692aac4dcb3fa2f4902358ce450ea4d7
Both payments are on their chains and locked to the same secret hash 5d886ea2012ae0bd4511b5cd120cb2077d034830, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 18c0777a39cbae477638c9165157d0fc692aac4dcb3fa2f4902358ce450ea4d7
- MakerPaymentSpent: 6b112355ef237573eb60a9eb554b16ef90c7dbe514162a0fa422ffe3c788c3ab
704c410c3a9aee4e6da88ced3a8b6b757310bd785021e17fac19546c925c7e00
Both payments are on their chains and locked to the same secret hash 5d886ea2012ae0bd4511b5cd120cb2077d034830, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f981dc1285ac6fd0057cf01ebd799d464ecbc0815afc250d87797cca4dd065e4
- TakerPaymentSent · TakerPaymentReceived: 704c410c3a9aee4e6da88ced3a8b6b757310bd785021e17fac19546c925c7e00
- TakerPaymentSpent: a96a8898c2102ed99579e61ed99d5664a9f92de11754ff19c795df6481f2a116
Reported by kdf-statsdb-8762.