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.
6785356d1abc7e9fb347e4e54a9b00d384df6562cd69a414eb6c9e5272737717
Both payments are on their chains and locked to the same secret hash a3d733b2c970f3892f4171742698bc3a596e8b46, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 6785356d1abc7e9fb347e4e54a9b00d384df6562cd69a414eb6c9e5272737717
1ef3e74a2c1be8a4202cfc55ba989d9b78b3e9ce5cf7d3bdc101adb315304b90
Both payments are on their chains and locked to the same secret hash a3d733b2c970f3892f4171742698bc3a596e8b46, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · f6126abfbfd053890874f82bbdd30019702be3aeb192889ee291578b85671fce
- TakerPaymentReceived · 1ef3e74a2c1be8a4202cfc55ba989d9b78b3e9ce5cf7d3bdc101adb315304b90
- TakerPaymentSpent · 91b30f0844755850311d79f8a340c195981477d64c05d4f35019274624b62f51
No anomalies were recorded against this swap.
Reported by kdf-statsdb.