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.
aad34b212a2b92003134b256299eb2111a0711d70e615ea558fa222060432f5d
Both payments are on their chains and locked to the same secret hash be9329aa56ec35f64d73f9dbe4c311628830b3fc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: aad34b212a2b92003134b256299eb2111a0711d70e615ea558fa222060432f5d
- MakerPaymentSpent: 579e99aff7ca64989c6f8e4027b4476c2eb9699bf7b68ae4cf9636e3c0213e55
a09db3dea225e06465823ae31698a33e0a0a4e5880e7245850fa2963aabdf191
Both payments are on their chains and locked to the same secret hash be9329aa56ec35f64d73f9dbe4c311628830b3fc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 63c9923a1bdb76bbe6ca742969cc3bfc32fa2381c3696dad77bf591f1d9ab3c8
- TakerPaymentSent · TakerPaymentReceived: a09db3dea225e06465823ae31698a33e0a0a4e5880e7245850fa2963aabdf191
- TakerPaymentSpent: f3843afbfda3974fdc76615b2f926b8eadfd63001611e1181a951427788a4d10
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.