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.
5f916b8b7bc99f501abe4f40362d612637ae5c7caf9417c75dc4920bb08708fb
Both payments are on their chains and locked to the same secret hash 8499d9624b32a08bd2c4daa79aec5571e1b0d6b6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 5f916b8b7bc99f501abe4f40362d612637ae5c7caf9417c75dc4920bb08708fb
- MakerPaymentSpent: 62ca31a82beeee61fac55365ee48af11618977937fd08c65df3da6d77b0f9f05
4ac0b3d0da94617f744145c41cc331eec6d34f759b7734fd0060b62ef619df28
Both payments are on their chains and locked to the same secret hash 8499d9624b32a08bd2c4daa79aec5571e1b0d6b6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4141f2bf2b4065d85ae4c6a13f728d0cea7bba4b355b8cf27deeb07af3515661
- TakerPaymentSent · TakerPaymentReceived: 4ac0b3d0da94617f744145c41cc331eec6d34f759b7734fd0060b62ef619df28
- TakerPaymentSpent: d5a94a44953e45a1c209895d64a022f2cd6e5367481a84f5c2f9f6ac0c94de57
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.