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.
eab086e0f7ce0a59f9802114176dc2780f2254d201784e5db9fd2b0bededbe69
Both payments are on their chains and locked to the same secret hash 4d6b182f712f942534e8c3c7299edef87ac77859, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · eab086e0f7ce0a59f9802114176dc2780f2254d201784e5db9fd2b0bededbe69
- MakerPaymentReceived · eab086e0f7ce0a59f9802114176dc2780f2254d201784e5db9fd2b0bededbe69
- MakerPaymentSpent · 428d72277408d71e94e1b1f6719cc65165234cbefa99478a040bafda1cc4c5fb
ec2c2e41b37a4898f53a518e2c016a67ca100f4f4ccd4102c07824861682c3c5
Both payments are on their chains and locked to the same secret hash 4d6b182f712f942534e8c3c7299edef87ac77859, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · c7cc6e151b1d491bcc19d73e4401b34318d8993251ea1e8268607388948e366b
- TakerPaymentReceived · ec2c2e41b37a4898f53a518e2c016a67ca100f4f4ccd4102c07824861682c3c5
- TakerPaymentSpent · 374a956d7dad73569cc3be5695dc6cb7c1155335f763246fa955726c21454285
- TakerFeeSent · c7cc6e151b1d491bcc19d73e4401b34318d8993251ea1e8268607388948e366b
- TakerPaymentSent · ec2c2e41b37a4898f53a518e2c016a67ca100f4f4ccd4102c07824861682c3c5
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.