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.
a5057fcf8ba3e4eec60fc6faf88ca64f22ed7f1aa518b344ed45c35cf51d8806
Both payments are on their chains and locked to the same secret hash d8b0aa03fe7d6bd4948551eef3de713b0872c400, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · a5057fcf8ba3e4eec60fc6faf88ca64f22ed7f1aa518b344ed45c35cf51d8806
d0e808f061536b38009531e5a264700e3f8ecff83470361595daa875d9cf950f
Both payments are on their chains and locked to the same secret hash d8b0aa03fe7d6bd4948551eef3de713b0872c400, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · aad6efa17bc7d5685bac5e8f9bbb2b14c236dbfe0fec824f1710ab0300f2807b
- TakerPaymentReceived · d0e808f061536b38009531e5a264700e3f8ecff83470361595daa875d9cf950f
- TakerPaymentSpent · 36c8c615fa205500f97be03b3c73a48d299df0edb690dcd0040a3c6c7c79e2b1
Reported by kdf-statsdb.