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.
2389db8fab05d21691c7ab29ddc7c91ab6466bebe118639fc28fe08edd62102f
Both payments are on their chains and locked to the same secret hash 7bffcb5733bd6a0f59c8e8c31983fb540dbf1d46, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2389db8fab05d21691c7ab29ddc7c91ab6466bebe118639fc28fe08edd62102f
- MakerPaymentSpent: 9038c83602ba164947e6a62b086e082c04d78487d265e122d3259e40ddab8d32
cdd754c400deb82ed112ba87923abdd2c0012b5fd663f8b41e70bd79bb790f3e
Both payments are on their chains and locked to the same secret hash 7bffcb5733bd6a0f59c8e8c31983fb540dbf1d46, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 654e161c80e79aa54e864443a0b9a1fae057a62a0df196b7b9c391b210545cd4
- TakerPaymentSent · TakerPaymentReceived: cdd754c400deb82ed112ba87923abdd2c0012b5fd663f8b41e70bd79bb790f3e
- TakerPaymentSpent: 11da6c94fbc1b9d213e799a4f256e25e954517089c284104408d7a0d16678dd5
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.