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.
55dd020f165aa9bb6470d59dc7a4178b53429b2f9be77fe24f989e8c571ec545
Both payments are on their chains and locked to the same secret hash 11144dc868db9efe98bf3992d2f40fa0a156c330, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 55dd020f165aa9bb6470d59dc7a4178b53429b2f9be77fe24f989e8c571ec545
- MakerPaymentSpent: 36ff00621d05303bf0ca740fddde849bb675ef2ffde0c087489883fd03932f7f
81940f03138b41270d782d3093021d56e05cdf2edd808209b69dbe9a24e47075
Both payments are on their chains and locked to the same secret hash 11144dc868db9efe98bf3992d2f40fa0a156c330, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4ffb55d24290b74d9224cce1eae505bf0d046531a2413f9bab05123369fc13c1
- TakerPaymentSent · TakerPaymentReceived: 81940f03138b41270d782d3093021d56e05cdf2edd808209b69dbe9a24e47075
- TakerPaymentSpent: f2a5d3f2b48ad1dc368b3b0af867ec58f82d28ca4df0f73a1d9e05b2dd00d045
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.