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.
e4c38ed1c6717715cd09e2ee2a3cf16018f913076aa821a13feb0a0bfadb0993
Both payments are on their chains and locked to the same secret hash f500be77ae7daf2d6a9873c8954b542d7221d924, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: e4c38ed1c6717715cd09e2ee2a3cf16018f913076aa821a13feb0a0bfadb0993
da94ec846f8463225cbbd33cad19f0f901801e605032b3fad53499bf8e4f3746
Both payments are on their chains and locked to the same secret hash f500be77ae7daf2d6a9873c8954b542d7221d924, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: f0d5eac3369107f672b97b8574ba460b65820afc4daf70e1388397a3170d36b6
- TakerPaymentReceived: da94ec846f8463225cbbd33cad19f0f901801e605032b3fad53499bf8e4f3746
- TakerPaymentSpent: fde4ba0d1f9060aa72f78fc93ebf45f5ad2a7fd443732d6a0beb272a02036e3a
Reported by kdf-statsdb.