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.
649fa91f3da8909bb9846b4b6ce5d577b6d4708fd50ccae270414cd6d4f6f77f
Both payments are on their chains and locked to the same secret hash 279fd4e237a7d85165ae40dbd789e7a83a3dd66a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 649fa91f3da8909bb9846b4b6ce5d577b6d4708fd50ccae270414cd6d4f6f77f
- MakerPaymentSpent: 849c22b1c7d3cb9c1a0ad5ae20b81c095845e6bf2387b079bb4164ff8105cc47
2fa40b341f13a23be37605888ba6ce253e2a8732c004ca18fc3bad3df4fa9ce1
Both payments are on their chains and locked to the same secret hash 279fd4e237a7d85165ae40dbd789e7a83a3dd66a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bb831a77fb63af80f1b42e91120f9b46add727bf9f60e4c582d52a506bfeeb01
- TakerPaymentSent · TakerPaymentReceived: 2fa40b341f13a23be37605888ba6ce253e2a8732c004ca18fc3bad3df4fa9ce1
- TakerPaymentSpent: de2e154f868d2fa90fc8536275e9694017d6102f248adc86b64800c14a35045a
Reported by kdf-statsdb.