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.
20473354c32e75aa57cae444165e3b8ce0302a5e1d22a484fc306734bbe21660
Both payments are on their chains and locked to the same secret hash ceb438886fd0fb9fe62b3224090131c994c03d6e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 20473354c32e75aa57cae444165e3b8ce0302a5e1d22a484fc306734bbe21660
- MakerPaymentSpent: b4e2c32f3e7ffa8c1776f955c0a6b3bf12accdc45ecdc9bc8a6b676d57dcfff9
acb7c358b48af12dc300681eb06f9ae1170531ae5093f26aad79713975a6d81b
Both payments are on their chains and locked to the same secret hash ceb438886fd0fb9fe62b3224090131c994c03d6e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 23b9e7f01faa32cd94ee4f30c76b22887eeee38adc288a753356e22895e662e1
- TakerPaymentSent · TakerPaymentReceived: acb7c358b48af12dc300681eb06f9ae1170531ae5093f26aad79713975a6d81b
- TakerPaymentSpent: cf0510c20911bf7dde29863b846210c31f1833544b886b2f8d397ef24ac8cabf
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.