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.
6121778a7a85f0a0c7d9897911ffa650665ccc2b034a0aa87e12ce58e7f15c19
Both payments are on their chains and locked to the same secret hash 293c3c46e3e9f81b4fabc753a18b5cf1ff3a13a1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6121778a7a85f0a0c7d9897911ffa650665ccc2b034a0aa87e12ce58e7f15c19
- MakerPaymentSpent: f95b40c6c98b2f88f12ee3622641e7f3b0acce6b5386322335d34202da2d44a3
68ce31797e491f0ba66fd00124fff79213cae0e8695cdcbdc0f20ece6923793f
Both payments are on their chains and locked to the same secret hash 293c3c46e3e9f81b4fabc753a18b5cf1ff3a13a1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3f8707e9dc44de3d270d2bf894845538b04a38c3e4573aa87c25b78ca3f368a5
- TakerPaymentSent · TakerPaymentReceived: 68ce31797e491f0ba66fd00124fff79213cae0e8695cdcbdc0f20ece6923793f
- TakerPaymentSpent: dc59a53b8ea84273cb519c1eb733335e421815e80db6384b086876d79b284eb3
Reported by kdf-statsdb.