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.
123088d26414f4b5e78e43cc5990e9cefe6ec2e7254f3f29a38f5501b6b8f6a0
Both payments are on their chains and locked to the same secret hash bde53ff7ad899bbb9e4fc483a39cb2c0916efd2f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 123088d26414f4b5e78e43cc5990e9cefe6ec2e7254f3f29a38f5501b6b8f6a0
- MakerPaymentSpent: 3b37404c206417f4e203da5857fc1deff4d5d18ce3017ef332cfdaa5a783eebb
a02dba17ae11cfd0fdc2e4b8d990d8f0f92402ea9464263222c17c6c9eccacce
Both payments are on their chains and locked to the same secret hash bde53ff7ad899bbb9e4fc483a39cb2c0916efd2f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e34f97a28a3fb6732e757cf43d68f1a5c7f6db57b2955bf6fcbcb8b14d5fabbe
- TakerPaymentSent · TakerPaymentReceived: a02dba17ae11cfd0fdc2e4b8d990d8f0f92402ea9464263222c17c6c9eccacce
- TakerPaymentSpent: 68e3e4f9e38c62db3ee5684ff445429edc52cb147fed28c96a2982bda2b2edde
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.