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.
30b7267d28829f1b3678d072c648367b36d8d649aca43ce80a6e4ff98adce72f
Both payments are on their chains and locked to the same secret hash 414f34fecf21841ab04b9decf60d62054ac075eb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 30b7267d28829f1b3678d072c648367b36d8d649aca43ce80a6e4ff98adce72f
- MakerPaymentSpent: 01210832978f64c9e33d3766df58791729c13382d6eebe351c453a284db69e2d
88190e20f0ac717afc3aa18ea12da74b28f8d903cad4cc0280e8118edae15aae
Both payments are on their chains and locked to the same secret hash 414f34fecf21841ab04b9decf60d62054ac075eb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 133736a9f5fde76532bd6beeb75fcfa6b885f7b022da11b649c4256fe3a0e461
- TakerPaymentSent · TakerPaymentReceived: 88190e20f0ac717afc3aa18ea12da74b28f8d903cad4cc0280e8118edae15aae
- TakerPaymentSpent: 0ac1749d52588277451f4c5233a5c62b7b79fb8c3eddc2bf7904202e7f5ba168
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.