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.
f3e7b4e66fe6d5e5d5e8a7379f7728389bba9fd2db6d301a9c42b54d56c9d8ff
Both payments are on their chains and locked to the same secret hash e6bf07d526963f795659f88ca41ca8b70d8629e1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · f3e7b4e66fe6d5e5d5e8a7379f7728389bba9fd2db6d301a9c42b54d56c9d8ff
34e47761881abb665b1e3e2a02425cd866e585c281c5ab198da846639f8fc4e4
Both payments are on their chains and locked to the same secret hash e6bf07d526963f795659f88ca41ca8b70d8629e1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 028f94c30f10c89bf39b3d4fd1c4fecd0dd02c29b331fd0b3b55cf5812b5c90b
- TakerPaymentReceived · 34e47761881abb665b1e3e2a02425cd866e585c281c5ab198da846639f8fc4e4
- TakerPaymentSpent · 09845d4d2fb96efe63ae09c9f0ba6c25ab15eefcb8527550a902d2d214d30a6d
Reported by kdf-statsdb.