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.
73c05aa8ff07b29b54bd761547e04268c5da412c48d99549760e5cf18c280b8c
Both payments are on their chains and locked to the same secret hash 361c03159b7191867b8d37241156724f8741ceae, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 73c05aa8ff07b29b54bd761547e04268c5da412c48d99549760e5cf18c280b8c
70b1ddc83f0c32efaabcd1613effd255b7e09074245f985f02023dc8f385937d
Both payments are on their chains and locked to the same secret hash 361c03159b7191867b8d37241156724f8741ceae, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · ec51df8b7164de21b2d34fdbddc5ac0cfb6284863d5bc72066056d39fbfb8a1c
- TakerPaymentReceived · 70b1ddc83f0c32efaabcd1613effd255b7e09074245f985f02023dc8f385937d
- TakerPaymentSpent · d373203fabe1586fe07198e7765bf36438dff13784b4dde46562431ac8aadb7b
No anomalies were recorded against this swap.
Reported by kdf-statsdb.