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.
c97320d1d2372dab9f3d9344c6d025f72d34fa9443da4963ec7d1f403da68b0a
Both payments are on their chains and locked to the same secret hash b00a715e0bd57ba9870108d7354cedb9e31b4d67, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c97320d1d2372dab9f3d9344c6d025f72d34fa9443da4963ec7d1f403da68b0a
- MakerPaymentSpent: 087ed983dd4e5441d0661b70360fb88d1131dc8d8fe44dbcd006cc7617e78486
a2b77af0f2b9368061feac90530ec0946ce9249e9183fdd69394ffd638ad5ada
Both payments are on their chains and locked to the same secret hash b00a715e0bd57ba9870108d7354cedb9e31b4d67, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e1f58eac89b4c022096b5b8e08c6c25e547ef37d3aed4849d9fb973642c71cbe
- TakerPaymentSent · TakerPaymentReceived: a2b77af0f2b9368061feac90530ec0946ce9249e9183fdd69394ffd638ad5ada
- TakerPaymentSpent: 139310d67140dd6a24bf419b1add987d06f43f18692649b01dd98fedc86023f1
Reported by kdf-statsdb-8762.