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.
c570a118730943fb78113ed7a3ee824ebd3ddacd5f43e1cf181340bf8e155e7f
Both payments are on their chains and locked to the same secret hash 54fdd014add0da5df7f02aa08d87bb27961dc655, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · c570a118730943fb78113ed7a3ee824ebd3ddacd5f43e1cf181340bf8e155e7f
- MakerPaymentReceived · c570a118730943fb78113ed7a3ee824ebd3ddacd5f43e1cf181340bf8e155e7f
- MakerPaymentSpent · dbdc28fb1f66c7731cf9ac3f9ed7d2de15464c3ee89bc668e4205281c6cac30b
4cc7715a0717260d052bef84769a888a341dfc17f0f7433a4063c71f48020b2d
Both payments are on their chains and locked to the same secret hash 54fdd014add0da5df7f02aa08d87bb27961dc655, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 2b82f6144082438879c2c3e941866b95169f5d4e794be05472504d6253261d05
- TakerPaymentReceived · 4cc7715a0717260d052bef84769a888a341dfc17f0f7433a4063c71f48020b2d
- TakerPaymentSpent · 549ed5d3069df10fb0a22282c8e0c1e7451559bf6bf42f6d436c4b0d8a0e104a
- TakerFeeSent · 2b82f6144082438879c2c3e941866b95169f5d4e794be05472504d6253261d05
- TakerPaymentSent · 4cc7715a0717260d052bef84769a888a341dfc17f0f7433a4063c71f48020b2d
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.