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.
1d7fb7dde33f815e19ac0cc25a8f5921e157d2cb59516225586ffe58db304e72
Both payments are on their chains and locked to the same secret hash c0955e90df759ee0efb11ac37494894df69b287c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1d7fb7dde33f815e19ac0cc25a8f5921e157d2cb59516225586ffe58db304e72
- MakerPaymentSpent: 1d9fc7a9c711af7e70ed5d2561fbce16b29903367756816726af21f374f7b7cb
81e5ae4334832bbae8d4937c77c71c313637b8c20ed785ff1c46746185403290
Both payments are on their chains and locked to the same secret hash c0955e90df759ee0efb11ac37494894df69b287c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 58dbf0f3000b0bc08886ce47b5ad227e4646b335753434fca8287b85e9783e73
- TakerPaymentSent · TakerPaymentReceived: 81e5ae4334832bbae8d4937c77c71c313637b8c20ed785ff1c46746185403290
- TakerPaymentSpent: 74cfcdfd4aab0686c2fa7d0c6a262cc50c02f322a402cb4f2a8af4a16705bad7
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.