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.
c8b1734ea81c0faa8a1df6ed6afa207ae92ac0b20d8697af633205b37c0dd0f3
Both payments are on their chains and locked to the same secret hash 57e10b15a3b4eafa5d2b466bda729b0c3deba805, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · c8b1734ea81c0faa8a1df6ed6afa207ae92ac0b20d8697af633205b37c0dd0f3
c25bdcf094cf24ea758d038d61e2881f4ba7abc82febfc75482d4d8ca911e63b
Both payments are on their chains and locked to the same secret hash 57e10b15a3b4eafa5d2b466bda729b0c3deba805, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · fac50c16ba0e77ef34c704c74211954e456fa1304a333bfd943a41e97a0bbaac
- TakerPaymentReceived · c25bdcf094cf24ea758d038d61e2881f4ba7abc82febfc75482d4d8ca911e63b
- TakerPaymentSpent · 5d531b0fa078b0dd8755b0171cb15d34f4f46e37eff1efdf7a0f426ebb8e46b8
No anomalies were recorded against this swap.
Reported by kdf-statsdb.