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.
0cec416ccac491b72fe9b757eeadaea02001a96eb323fdc3524e43365c2fa469
Both payments are on their chains and locked to the same secret hash d9ee5ed1c760f0e8dfbd373a48a54c454dfa5bc8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 0cec416ccac491b72fe9b757eeadaea02001a96eb323fdc3524e43365c2fa469
- MakerPaymentReceived · 0cec416ccac491b72fe9b757eeadaea02001a96eb323fdc3524e43365c2fa469
- MakerPaymentSpent · a65a0ae80a4f7b01bcd1c9e9b3dbdcb1b7d735326ae5e384a3b1ecb0a531edd5
3ef4d6c8f4365b554ad9515367af9ee5a6118521f966f2086f5def63b6916d35
Both payments are on their chains and locked to the same secret hash d9ee5ed1c760f0e8dfbd373a48a54c454dfa5bc8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 295203d4b3e2c8ab65a858e183438e9830849dd57109975d8c3d62986f25c83c
- TakerPaymentReceived · 3ef4d6c8f4365b554ad9515367af9ee5a6118521f966f2086f5def63b6916d35
- TakerPaymentSpent · b2abbb0bfc5274ffbf1c8a55d258aff8491cf66e3faa6ac6a358f180a31b0b6d
- TakerFeeSent · 295203d4b3e2c8ab65a858e183438e9830849dd57109975d8c3d62986f25c83c
- TakerPaymentSent · 3ef4d6c8f4365b554ad9515367af9ee5a6118521f966f2086f5def63b6916d35
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.