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.
c166519000ffd0266661f18b05c9982a7ae4ba6cf274f06b7a36ea2ea4bd87d8
Both payments are on their chains and locked to the same secret hash 4ab7f71d97537be363e01ca4361a28f7339de252, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · c166519000ffd0266661f18b05c9982a7ae4ba6cf274f06b7a36ea2ea4bd87d8
- MakerPaymentReceived · c166519000ffd0266661f18b05c9982a7ae4ba6cf274f06b7a36ea2ea4bd87d8
- MakerPaymentSpent · b6d478e1513a34efe36f8e38f17594c61d6da814b8258c82b757c188b1bc7ff8
026b02310bf42ec1295eeb8d0aeaf336546fffbba1ac6e28617f1e1a5e21a598
Both payments are on their chains and locked to the same secret hash 4ab7f71d97537be363e01ca4361a28f7339de252, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 101b10b4803d41265342117fdd5b0c091139fa35fdb79b71f9648c80a3d93c22
- TakerPaymentReceived · 026b02310bf42ec1295eeb8d0aeaf336546fffbba1ac6e28617f1e1a5e21a598
- TakerPaymentSpent · 821d1b3f818e4a83cc8ce338a1b24a4865a65ed4871e0556f57d8b5e023b7451
- TakerFeeSent · 101b10b4803d41265342117fdd5b0c091139fa35fdb79b71f9648c80a3d93c22
- TakerPaymentSent · 026b02310bf42ec1295eeb8d0aeaf336546fffbba1ac6e28617f1e1a5e21a598
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.