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.
5e1ca1cdfee5005bf90c212472704c939705eac40b3cf71b4fb5363d21317b2e
Both payments are on their chains and locked to the same secret hash 43a4d79c49154676a82c3a04114923520815a92f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 5e1ca1cdfee5005bf90c212472704c939705eac40b3cf71b4fb5363d21317b2e
- MakerPaymentReceived · 5e1ca1cdfee5005bf90c212472704c939705eac40b3cf71b4fb5363d21317b2e
- MakerPaymentSpent · 49f1ad181ec35fd0c212ed786887c9234e06c661b5fc79af25368636b4b01fdf
ff11bcaa1fd03c35571b3d1d6cff0abbbfd3d3baaf8b5475c7266eceed786387
Both payments are on their chains and locked to the same secret hash 43a4d79c49154676a82c3a04114923520815a92f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 79a0ddc5350e0ba4930a30a0aa0bce55331b6c48a8090c094d4c5925cfc04ff5
- TakerPaymentReceived · ff11bcaa1fd03c35571b3d1d6cff0abbbfd3d3baaf8b5475c7266eceed786387
- TakerPaymentSpent · 6f49c90a187d51fca090cd3a352249475358f0a8cfe802e5eeadc8273cbd0d0d
- TakerFeeSent · 79a0ddc5350e0ba4930a30a0aa0bce55331b6c48a8090c094d4c5925cfc04ff5
- TakerPaymentSent · ff11bcaa1fd03c35571b3d1d6cff0abbbfd3d3baaf8b5475c7266eceed786387
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.