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.
40ceb751265a233162833320d5ebac543e42dc7e6fb4341f147c1fc55dae4c68
Both payments are on their chains and locked to the same secret hash 1b7b52a06a5d90ca9c3568a0b69527a7f91be9a0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 40ceb751265a233162833320d5ebac543e42dc7e6fb4341f147c1fc55dae4c68
- MakerPaymentReceived · 40ceb751265a233162833320d5ebac543e42dc7e6fb4341f147c1fc55dae4c68
- MakerPaymentSpent · 09ecef5cd8328af007ec55959d91df527b5ff6f451fd37ad16dcb15b4c1040a8
f74e3abbde7b70ca5bc67ea55210939c8ee72981e6cd816ecf7284687cc9b130
Both payments are on their chains and locked to the same secret hash 1b7b52a06a5d90ca9c3568a0b69527a7f91be9a0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 4f349eae9ba368a9c74d31eaf9a8da6e59aa782fea156b723fcdccb0cac3dbee
- TakerPaymentReceived · f74e3abbde7b70ca5bc67ea55210939c8ee72981e6cd816ecf7284687cc9b130
- TakerPaymentSpent · 26f230f1919cacbb8c508ce760bc48d3800c9e6fe212dbb062e43eac6c0c293a
- TakerFeeSent · 4f349eae9ba368a9c74d31eaf9a8da6e59aa782fea156b723fcdccb0cac3dbee
- TakerPaymentSent · f74e3abbde7b70ca5bc67ea55210939c8ee72981e6cd816ecf7284687cc9b130
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.