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.
2a6f340331ad5d5155c3b767dd244013b968746593029604776bd1466222c482
Both payments are on their chains and locked to the same secret hash bfdfbfbadc1685099c96174365ff12bb403ed2f1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2a6f340331ad5d5155c3b767dd244013b968746593029604776bd1466222c482
- MakerPaymentSpent: 5002a161147fcde04826b8b4d3936652cf38de23600a1809c2489d4c43d01ec1
fcfc5e9feab58c7879892f7e1b4c2af12d91f3f2c418f8b7a02593a8ffa431be
Both payments are on their chains and locked to the same secret hash bfdfbfbadc1685099c96174365ff12bb403ed2f1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9128a00459ca428365166ebbc87f4ef770a633be0b12e23768ab0b915e72b83a
- TakerPaymentSent · TakerPaymentReceived: fcfc5e9feab58c7879892f7e1b4c2af12d91f3f2c418f8b7a02593a8ffa431be
- TakerPaymentSpent: 58cb246cec42b1cef94e61506e6ef396f300aaa96e1a85b7bb3de4adf66793ec
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.