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.
9861290abeafd292cb07d927d4dd795f41add52e193955ed789f6f90667d83e9
Both payments are on their chains and locked to the same secret hash 4264ee0cb6e91f0ed5d5b8f588823a3305d1fb18, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9861290abeafd292cb07d927d4dd795f41add52e193955ed789f6f90667d83e9
- MakerPaymentSpent: f1d5505153b140fdc47f16185e15a4e747aa104c4356d35d0337e736fb3aa762
45b145d58415eb57cde4b4ca545cd60b937bb1958780c8b3ed491349097abf07
Both payments are on their chains and locked to the same secret hash 4264ee0cb6e91f0ed5d5b8f588823a3305d1fb18, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b92e8ec501f18d361ee255885f4b3996dba414caa53f78b518ee941803f0f45e
- TakerPaymentSent · TakerPaymentReceived: 45b145d58415eb57cde4b4ca545cd60b937bb1958780c8b3ed491349097abf07
- TakerPaymentSpent: ffe6f082043bab337931fb772fa8d94c76f806b34e35abb88073885e651f602e
Reported by kdf-statsdb-8762.