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.
8ec99301f4a00ac94018c0d6593469b2b3f73c244ecc1d47126e68ecbf78c703
Both payments are on their chains and locked to the same secret hash 7aef957fc77cfaf0178d66f50b4546cf992ee97f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8ec99301f4a00ac94018c0d6593469b2b3f73c244ecc1d47126e68ecbf78c703
- MakerPaymentSpent: 3e9c00f8c91b3d9403ee22fd65bc790338caec15e2db0292f04deba1d3ffbc46
306c494281b633dab5c86c304039c925ef59274b8627f4d081e63559a2ea1de0
Both payments are on their chains and locked to the same secret hash 7aef957fc77cfaf0178d66f50b4546cf992ee97f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 23787bf15f1f497f14a067f67c03c283b8523412d45ca605f89f284339eb28d6
- TakerPaymentSent · TakerPaymentReceived: 306c494281b633dab5c86c304039c925ef59274b8627f4d081e63559a2ea1de0
- TakerPaymentSpent: 281ee75d9d30b5cacada6694b3a6d38550cf57340714e1af1cd38088b4a44968
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.