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.
da8e48a8327664c96ed8ed17963e7c524b34c92b2cfe7ca065559cd50ae66f7e
Both payments are on their chains and locked to the same secret hash 2bb20e95843cd0e62143fc808392e2ba86df791e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: da8e48a8327664c96ed8ed17963e7c524b34c92b2cfe7ca065559cd50ae66f7e
- MakerPaymentSpent: 2849f3719edf77bfaab334f7accba23072f4c000f7e8179095f2b489f0f4f121
09792d8b6414c64d1557b4414332ddf4daf4946f4d496a95af2dfccc20111f41
Both payments are on their chains and locked to the same secret hash 2bb20e95843cd0e62143fc808392e2ba86df791e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e8ccafff4068bd7b2a9614a24cca019183209cf974f43d823c4e3642a4ea601f
- TakerPaymentSent · TakerPaymentReceived: 09792d8b6414c64d1557b4414332ddf4daf4946f4d496a95af2dfccc20111f41
- TakerPaymentSpent: 46bab2427593656fc206702873508236b120f614523d3356548c3dfb85161769
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.