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.
ca9cea0be8dc956a223cbd2b89eaf2656ae20935904457b00f14952922925cfd
Both payments are on their chains and locked to the same secret hash e25746897381328ae395e6fa7a414f2f5516c2c6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ca9cea0be8dc956a223cbd2b89eaf2656ae20935904457b00f14952922925cfd
- MakerPaymentSpent: 28d82806da2263b22a157dd730232f974cebbc563f250750ca061e0faedfb376
43b015c31b96c14770c2fdd2450dff506117c6e880fe1a376689d66ced2c465c
Both payments are on their chains and locked to the same secret hash e25746897381328ae395e6fa7a414f2f5516c2c6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ce76e746c5c41298c1f6816bee202912e852288b774bdd95a6fdbe46e51ba8b0
- TakerPaymentSent · TakerPaymentReceived: 43b015c31b96c14770c2fdd2450dff506117c6e880fe1a376689d66ced2c465c
- TakerPaymentSpent: f77060f731c0492bea332f4965beb8463856275af26081ed0d88bbe7d5cde0db
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.