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.
255ac4cc78d6a3a646e0f43f149f20908b80217cd6e5b2ad8efb72e47227a07a
Both payments are on their chains and locked to the same secret hash 2f73b5d91382204b25bdced464141ae6d7c5a948, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 255ac4cc78d6a3a646e0f43f149f20908b80217cd6e5b2ad8efb72e47227a07a
ba5aa004f91d53d41a6de24c4313bf276f3ba5d719247f57ec574fa826bf722c
Both payments are on their chains and locked to the same secret hash 2f73b5d91382204b25bdced464141ae6d7c5a948, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · b8838341a0dfd87b05df1d234f73eed30f68bb03c91e90c96caf1b3e5c979ae5
- TakerPaymentReceived · ba5aa004f91d53d41a6de24c4313bf276f3ba5d719247f57ec574fa826bf722c
- TakerPaymentSpent · 9a3ea8607ab475a25e05b94389e90eba7576847224c0cad517a338f48b051e86
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.