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.
9de85ec6a222381f7a2c0e177a70e60b2e715a9ab4b6ac3f31f5e19e4bdc099e
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 9de85ec6a222381f7a2c0e177a70e60b2e715a9ab4b6ac3f31f5e19e4bdc099e
- MakerPaymentSpent: 6a3f95ea72627d352d8909b9a7e79f9284651d070633f52fa80ccf46cde17be0
bb9711c82ca26e98a8b9fb185adadec324be8a097b440a1f2b8c56aef0a91533
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 05cc63693b8eb160b2885aea8e4842ba98e007397813efca98b651bb55274c06
- TakerPaymentSent · TakerPaymentReceived: bb9711c82ca26e98a8b9fb185adadec324be8a097b440a1f2b8c56aef0a91533
- TakerPaymentSpent: 6452127acce08c28dbe4b1403da84f92e59d98ed78780ba307b56ee30a681a21
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.