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.
3fa5e98fe3f0e368190623be1a1368013de9851d04d654494184668761e148ae
Both payments are on their chains and locked to the same secret hash dfc5a023d031a4af143f0d05c219c35a14fe7cb7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 3fa5e98fe3f0e368190623be1a1368013de9851d04d654494184668761e148ae
- MakerPaymentSpent: 429eb7b863c6b4dae74a58b7e0c56c14b8b59fcfb40d295e608e742284f1c5e3
55d78d0c0168dfcd78003bce825a3612556639252f269c0b031f0f7b455b7bfd
Both payments are on their chains and locked to the same secret hash dfc5a023d031a4af143f0d05c219c35a14fe7cb7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 88b79ed721c8f3247a97b5354baf11e16a44753374979e1a9dd4e4d1f11c2f6e
- TakerPaymentSent · TakerPaymentReceived: 55d78d0c0168dfcd78003bce825a3612556639252f269c0b031f0f7b455b7bfd
- TakerPaymentSpent: b35b197cb2cd45e84681e853c844ba36d26b46a36431f2e806e15ce7f2837f1d
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.