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.
cc56dfd363763dc066301ec10ec80fd41d25422a38a560b3d789b467f4af3086
Both payments are on their chains and locked to the same secret hash 6d2d442bb95938676b2ec571d12b8553d179686d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cc56dfd363763dc066301ec10ec80fd41d25422a38a560b3d789b467f4af3086
- MakerPaymentSpent: 0c3e6fd5949821d97c5767eec00dddf21f1e22c4633c0ae9b075692d3c474e24
12e77f37b15af60d38c642afb2261fa083180a3c77a9df5254f36bb7bbe54941
Both payments are on their chains and locked to the same secret hash 6d2d442bb95938676b2ec571d12b8553d179686d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 58aad5f584d15871d2109a69b2b15138fc1d3d290530748409072e6d3cf3fbd1
- TakerPaymentSent · TakerPaymentReceived: 12e77f37b15af60d38c642afb2261fa083180a3c77a9df5254f36bb7bbe54941
- TakerPaymentSpent: ff61c0aecdb7b6dc5c7739cb7a7ff992add40724565467189bd4815981c8e576
Reported by kdf-statsdb.