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.
3509d9f37b10bb42446ac80ae6617e4f255c4a370179ab1ed9e810f7d03965eb
Both payments are on their chains and locked to the same secret hash 3810006adbc159a1e5993119785eef84953afc10, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 3509d9f37b10bb42446ac80ae6617e4f255c4a370179ab1ed9e810f7d03965eb
013c96b397901195d52ed0f38754378699e62039adbcfd21099baf718c474f27
Both payments are on their chains and locked to the same secret hash 3810006adbc159a1e5993119785eef84953afc10, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · f876ed1b74e505a070339b2e1693902bd11fde6b01f7a2c2a475924ee5b0319d
- TakerPaymentReceived · 013c96b397901195d52ed0f38754378699e62039adbcfd21099baf718c474f27
- TakerPaymentSpent · e76aae923ae38fb831afe265891de7f7a8bc589fde730f53aac948895286fb42
No anomalies were recorded against this swap.
Reported by kdf-statsdb.