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.
9623978a3bfaac11ad4ed36def29d3619283557482d7e412cb96847f9c9cd367
Both payments are on their chains and locked to the same secret hash 00271951887aebefeb0ea044393e1c701429b6f8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · 9623978a3bfaac11ad4ed36def29d3619283557482d7e412cb96847f9c9cd367
- MakerPaymentSpent · b2975cf5faac8ae8d817c75fa30ce271b31d4e8d35c52ac49207f43f792e4bb5
b4e82f5321dc2958002e3e488916b38a377c588ad35cb405712ba2f94258f73c
Both payments are on their chains and locked to the same secret hash 00271951887aebefeb0ea044393e1c701429b6f8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · 750512b4b7664e2bdd70fb68b2a40625988f8e2ac3094c4f9f01d4b46655ec87
- TakerPaymentSent · b4e82f5321dc2958002e3e488916b38a377c588ad35cb405712ba2f94258f73c
No anomalies were recorded against this swap.
Reported by kdf-statsdb.