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.
6f7185f060d428fa5a17c621f5615cae41eb218d46ffafbc8d247588483ef1c4
Both payments are on their chains and locked to the same secret hash 1813ce08228366a6d003cba5f73cb4e0af70c58f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6f7185f060d428fa5a17c621f5615cae41eb218d46ffafbc8d247588483ef1c4
- MakerPaymentSpent: 73208711813a28e24206f0e345837f7bf526249bcfd8b246bab75b75293a8655
6755337f7ede7f89bfbe1e4aefe38fd22ffef41f99f72959567b75686fec62f8
Both payments are on their chains and locked to the same secret hash 1813ce08228366a6d003cba5f73cb4e0af70c58f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 606dda1248e091ebfba0c173f4fb4272ca4bd492458002c15cb7961c6df8862f
- TakerPaymentSent · TakerPaymentReceived: 6755337f7ede7f89bfbe1e4aefe38fd22ffef41f99f72959567b75686fec62f8
- TakerPaymentSpent: cda3888772381c2d015d8b2ade49afc51ab4c616ba3c224a270aa02350f71d99
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.