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.
c02331b9f83d9be16c4f9652b3f2b878f5e956c924191963572a5c97d423e8c3
Both payments are on their chains and locked to the same secret hash 24e0039bac69b14f8353a769d72cd3ae4b58d129, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: c02331b9f83d9be16c4f9652b3f2b878f5e956c924191963572a5c97d423e8c3
- MakerPaymentSpent: e4e944b83ddd2c374eeedf6ff1d5fdf4b4977dbe28fd47381bb7e414a36fc3a2
4a665338ceea7c9dd2c2a164190fcad6f1f8c13acd2dcd18eec7ac0c266382f6
Both payments are on their chains and locked to the same secret hash 24e0039bac69b14f8353a769d72cd3ae4b58d129, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8286a51895ad1b00f3641af6be782677d72626d686cbf3b7394a6e365e4a95d6
- TakerPaymentSent · TakerPaymentReceived: 4a665338ceea7c9dd2c2a164190fcad6f1f8c13acd2dcd18eec7ac0c266382f6
- TakerPaymentSpent: 504587ee265b5bd763cb4da4f11bcd072bcdcf7c97eb7bc81786f397c463f312
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.