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.
c5dcb8600ac4199d3da108fe34d9866531e97820374b4a1cb6dc4a40b267ac1b
Both payments are on their chains and locked to the same secret hash fc655a315550be40b7ee1eb97d4aee371f3a20a1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c5dcb8600ac4199d3da108fe34d9866531e97820374b4a1cb6dc4a40b267ac1b
- MakerPaymentSpent: 28f3400e1453dacab4e4becca2b24d3de94fff73d847472f8f048144c9dfdf55
4d46e4b285c26600d50e9c94007bdba6956f7c70e93953f24c3c413accbff2f2
Both payments are on their chains and locked to the same secret hash fc655a315550be40b7ee1eb97d4aee371f3a20a1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 64f96bcf0c166daaf2513012da12b496af5f1e3d2b290aa6543ee9a337d19fb1
- TakerPaymentSent · TakerPaymentReceived: 4d46e4b285c26600d50e9c94007bdba6956f7c70e93953f24c3c413accbff2f2
- TakerPaymentSpent: aac0c9b0a586808c991f0f86560bb09838243d4a8d3ea31d4004a23c2e5312c2
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.