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.
46e6115e47e105520550f6184ab040f94edf4f48124afd92fadd248564f9fa79
Both payments are on their chains and locked to the same secret hash 14065f95e49664bcb9706399da28cd3f4b16fcf3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 46e6115e47e105520550f6184ab040f94edf4f48124afd92fadd248564f9fa79
31e978be97fb82ff968e5809a0c77a6b51e0ee42a41b8a7aaf6823a1db27550d
Both payments are on their chains and locked to the same secret hash 14065f95e49664bcb9706399da28cd3f4b16fcf3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: d3e301505f1d04687a6656c5e37c5693c718ed68583992bd583691a965fddf35
- TakerPaymentReceived: 31e978be97fb82ff968e5809a0c77a6b51e0ee42a41b8a7aaf6823a1db27550d
- TakerPaymentSpent: d27458adc5e541ba70a8c9238a6cfdfcb7390789dbe5255e03645c00bcb03300
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.