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.
974354789344737e06069049562391bc5a56f4cccb99934b9ad788fbcc4fc6dd
Both payments are on their chains and locked to the same secret hash 02ac3c296591195ce9fb60516be24bb2471f47ce, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 974354789344737e06069049562391bc5a56f4cccb99934b9ad788fbcc4fc6dd
- MakerPaymentSpent: 013cf41fd0f7ec6b0b046c5fe78d6151720056c77561dbcee4c4ec7c4554d0ce
02eb20123cef5b002224a672ce84fb8ce313531f05989a98743966029ef326fc
Both payments are on their chains and locked to the same secret hash 02ac3c296591195ce9fb60516be24bb2471f47ce, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c19a3f7d5ca7a00a9e3f015aeb9f0594c3ac033819e1dcbfaea1963d7245f04d
- TakerPaymentSent · TakerPaymentReceived: 02eb20123cef5b002224a672ce84fb8ce313531f05989a98743966029ef326fc
- TakerPaymentSpent: 7c0c75a2fdbc137ddf249133ddc1bcbd7ccb56aae06dd85106773453e0baa16d
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.