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.
74bcf3cc0eb8d3217886d4d7fd3dcb46c86e0be4da3d93c44ca89097f8313d29
Both payments are on their chains and locked to the same secret hash d2372004652e94d1ab84ff6a6bd7cd70ee85bb1f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 74bcf3cc0eb8d3217886d4d7fd3dcb46c86e0be4da3d93c44ca89097f8313d29
b7c65de731f521a4ae67cb7e3546fe7869b90d0fd8657df867487d3a5c23ef75
Both payments are on their chains and locked to the same secret hash d2372004652e94d1ab84ff6a6bd7cd70ee85bb1f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · fb0238ea5c445bbdfc7c0ac37a0f00bcd6e5de38d795679235dec0f303488ce3
- TakerPaymentReceived · b7c65de731f521a4ae67cb7e3546fe7869b90d0fd8657df867487d3a5c23ef75
- TakerPaymentSpent · 293941c3d95426e8ef6d746c123e30c615f019dfced88fb500262957e3fe8da1
No anomalies were recorded against this swap.
Reported by kdf-statsdb.