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.
aa22427896c3f3f85ff81ac79feacf3a541453b9816c6364026febc7d759c095
Both payments are on their chains and locked to the same secret hash 4b86bc977cc11bdaeb78010306bc2b7f1aa4ddfd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · aa22427896c3f3f85ff81ac79feacf3a541453b9816c6364026febc7d759c095
10414007227c0d4211a753e284949d76a8b1909b3c61407128a385e43271917d
Both payments are on their chains and locked to the same secret hash 4b86bc977cc11bdaeb78010306bc2b7f1aa4ddfd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · a36105d923b000476acc3142d8b4ffb974112119c139a919a0c7e63d566924c3
- TakerPaymentReceived · 10414007227c0d4211a753e284949d76a8b1909b3c61407128a385e43271917d
- TakerPaymentSpent · ba0e4a35a27f67b8104fc349ba02f06a41ddd0544e93790648706e2825db53b4
No anomalies were recorded against this swap.
Reported by kdf-statsdb.