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.
f5880ba00e09e575f6698703357fec725ba00866e959e5aaef9bde47d5a1d7fb
Both payments are on their chains and locked to the same secret hash 3504e96d4880bb37fe6b153deceec0c8a14921c6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · f5880ba00e09e575f6698703357fec725ba00866e959e5aaef9bde47d5a1d7fb
- MakerPaymentReceived · f5880ba00e09e575f6698703357fec725ba00866e959e5aaef9bde47d5a1d7fb
- MakerPaymentSpent · 3408483208afb71839ed2beafbf0990ba25d1fd9a915482974a75ff16c4d343c
b0c761a8652409738c2122b437fd2488805d4eac86bad1611c8900f1e3e0b9f0
Both payments are on their chains and locked to the same secret hash 3504e96d4880bb37fe6b153deceec0c8a14921c6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · b31a4f1182819c03c2055f42cbb0ab70e74a33cee9767a0f9c1b3149ba2921e9
- TakerPaymentReceived · b0c761a8652409738c2122b437fd2488805d4eac86bad1611c8900f1e3e0b9f0
- TakerPaymentSpent · 01e5070fe3c75109666f28b6e19535daae401e0aa360a7a3ee4e290d0c09f8c3
- TakerFeeSent · b31a4f1182819c03c2055f42cbb0ab70e74a33cee9767a0f9c1b3149ba2921e9
- TakerPaymentSent · b0c761a8652409738c2122b437fd2488805d4eac86bad1611c8900f1e3e0b9f0
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.