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.
09755eee6bdf7de0db6106688fea9fd27d866fe2016ef885be8f0520a593ae8d
Both payments are on their chains and locked to the same secret hash fb4fbefb0c926878c08ce359bdee3953c802cabc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 09755eee6bdf7de0db6106688fea9fd27d866fe2016ef885be8f0520a593ae8d
f2d60df72d9ce9c41f9e0e0af0b6ae16845e893f983743cd988eee122723faee
Both payments are on their chains and locked to the same secret hash fb4fbefb0c926878c08ce359bdee3953c802cabc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · a73b35d0690a96339010b17fa892a597fee70fb5563691c0f9c07fe75d141260
- TakerPaymentReceived · f2d60df72d9ce9c41f9e0e0af0b6ae16845e893f983743cd988eee122723faee
- TakerPaymentSpent · aa1a419145990331166e9f5f726c04e68da83038fd37c20d25903719db233747
Reported by kdf-statsdb.