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.
0d2f822a69cb6bc5f253b27afc8cb428f7bf381be106e084dbe981b46f37a856
Both payments are on their chains and locked to the same secret hash 71b05d2c54cf14eb320bd5bb97cc20136616974c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0d2f822a69cb6bc5f253b27afc8cb428f7bf381be106e084dbe981b46f37a856
- MakerPaymentSpent: da493bebfd039ed5644991716c068fe655f4ef9a2993f83afbb5ba0f5c756c6e
fc76483934a53da98bb46a727f98c2126abfcd8ac3c7143a7d4c8e6182665549
Both payments are on their chains and locked to the same secret hash 71b05d2c54cf14eb320bd5bb97cc20136616974c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fefcf6381c14b669ec50886fb89264c5c05ead3cd89bd7f796872964352bec28
- TakerPaymentSent · TakerPaymentReceived: fc76483934a53da98bb46a727f98c2126abfcd8ac3c7143a7d4c8e6182665549
- TakerPaymentSpent: 7e02f5ac5e7d9e4312a4086179e21253f903b919d422d824fcd13c8cd357a97a
Reported by kdf-statsdb.