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.
6c621b9f8d0cd5d960d5aea4b1faea665cd7a55edf7f509ebdc7e447df1f6a51
Both payments are on their chains and locked to the same secret hash 3579ee9e68efbacc13adeaca781b0396c94946ca, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 6c621b9f8d0cd5d960d5aea4b1faea665cd7a55edf7f509ebdc7e447df1f6a51
- MakerPaymentSpent: 7e88568e37eddffb612281bdba7329ac4aaa9c8c8f2dded8084be30e8780db1d
02db263f2660fdf025a6df75e2beffe29ebb82035d223a0d7d74c8eb1d038a3f
Both payments are on their chains and locked to the same secret hash 3579ee9e68efbacc13adeaca781b0396c94946ca, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a8c44e115fc8700392cd8633d5a57072e47a97201b68ca74b45349d0b5be56c2
- TakerPaymentSent · TakerPaymentReceived: 02db263f2660fdf025a6df75e2beffe29ebb82035d223a0d7d74c8eb1d038a3f
- TakerPaymentSpent: 8825e9eafc96fa1ab9108af55bb7efafcf559174165070d5ea74c1b2e4d80c94
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.