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.
01e369d3dd69d752ad5c21fc309c9c0d906f367c561bb0bb828a47df418b5ede
Both payments are on their chains and locked to the same secret hash f6cd69f8209e7e0a647b164016254cf64428d15e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 01e369d3dd69d752ad5c21fc309c9c0d906f367c561bb0bb828a47df418b5ede
- MakerPaymentReceived · 01e369d3dd69d752ad5c21fc309c9c0d906f367c561bb0bb828a47df418b5ede
- MakerPaymentSpent · 5b1392ea7ac67e4b27c0c0b462a86d3cba1b1e05dd985bb0c444a971396e6957
336c9a9153e7066d8e4f06e57321dd18c492db2f7a6a284fe58a572f36730422
Both payments are on their chains and locked to the same secret hash f6cd69f8209e7e0a647b164016254cf64428d15e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 1c2578a7558cedfb4200d4ece9566c918e96586e0319fd3479626c567b968006
- TakerPaymentReceived · 336c9a9153e7066d8e4f06e57321dd18c492db2f7a6a284fe58a572f36730422
- TakerPaymentSpent · 10538d62c82175e2039ac3e26b0e9f7f9b5946d900c687e33c0d570b01c7b504
- TakerFeeSent · 1c2578a7558cedfb4200d4ece9566c918e96586e0319fd3479626c567b968006
- TakerPaymentSent · 336c9a9153e7066d8e4f06e57321dd18c492db2f7a6a284fe58a572f36730422
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.