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.
03860684c19696e9d02ac9de7f410a8c871afbc71e5950c7bd250763140d907e
Both payments are on their chains and locked to the same secret hash c3e1462570ea88ae9851d92fa482668e77cf5acc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 03860684c19696e9d02ac9de7f410a8c871afbc71e5950c7bd250763140d907e
- MakerPaymentSpent: 7d3037d6cf1fc26b1bf1d6281f01a140370de13f9b4e89215d6b2a1eab1baa8f
72501573a30b5d130dee3cc4e237c092f400da98a0fd5b9ae259c451ac315a85
Both payments are on their chains and locked to the same secret hash c3e1462570ea88ae9851d92fa482668e77cf5acc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bcaa10873e5249dd06a5c3b9e7b521f9f65794ff4f183385212db6768bd9a78d
- TakerPaymentSent · TakerPaymentReceived: 72501573a30b5d130dee3cc4e237c092f400da98a0fd5b9ae259c451ac315a85
- TakerPaymentSpent: 5c6e9c6bb8afff49d741b1cd1f29224ca81b7280ec69db4087fa5e0674bd81e2
Reported by kdf-statsdb.