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.
10ce92da8c61282da003d22b7aa5ce3dee619e9c9dc3256dd96ad6069631d6a8
Both payments are on their chains and locked to the same secret hash e508a8c7cd8abcaf06e3fb0ee5e394bf8575cd79, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 10ce92da8c61282da003d22b7aa5ce3dee619e9c9dc3256dd96ad6069631d6a8
- MakerPaymentSpent: 2035d7dc5bd4ba02a90edf6c224e5b84644f682b39a2edc15f426f6fb8a0d861
e60d28cf45b2d8ad43656835d73ae16f2bcd9aa6224062fe8792e544235172b1
Both payments are on their chains and locked to the same secret hash e508a8c7cd8abcaf06e3fb0ee5e394bf8575cd79, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0b4e5881e218854e2a938ee79d0cc35f178fff2632e5df7e55f13397193105f5
- TakerPaymentSent · TakerPaymentReceived: e60d28cf45b2d8ad43656835d73ae16f2bcd9aa6224062fe8792e544235172b1
- TakerPaymentSpent: a9c49e41c95e7c8a62ff9e80e17a65f47cd40fe8b8137532ede8b91359067e8d
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.