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.
0d77b9b8154a754cd7dc00ae395383c3fe97c7491c379aaae3662567a481c3d2
Both payments are on their chains and locked to the same secret hash 96a07379e3e487e9b529045fab45043b0e63273a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0d77b9b8154a754cd7dc00ae395383c3fe97c7491c379aaae3662567a481c3d2
- MakerPaymentSpent: 27d446a4539aa3ff00624c897d12968052de52be6b35c4cd9c0485b3e1e227a0
39ae0c8161cc817d28904ab0b89be15ffe685bc4e967f650dd1845566b547fab
Both payments are on their chains and locked to the same secret hash 96a07379e3e487e9b529045fab45043b0e63273a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d70c33b841c7cc23517e719f2d85a182be1185df74a0fbf766d19b535434a382
- TakerPaymentSent · TakerPaymentReceived: 39ae0c8161cc817d28904ab0b89be15ffe685bc4e967f650dd1845566b547fab
- TakerPaymentSpent: 78df76650bc7981e9c46b48a5f5bd4636d2f866901d5055a7576458298097250
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.