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.
849c355be6b5c90abe2c56225a98335c9414dbba78bffec6ce36d177c704624d
Both payments are on their chains and locked to the same secret hash fb8e4f15ef8ef18b2d9e5d089afa85abb1d15822, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 849c355be6b5c90abe2c56225a98335c9414dbba78bffec6ce36d177c704624d
- MakerPaymentSpent: 3ef121e3432892e4ae4fdb28392671f4f8f38da3571a3bd9e41b3895a0636684
6f650600e9f65bdf60ad59b71b1657fe7a28019ca2567519d30fd137bd73c1df
Both payments are on their chains and locked to the same secret hash fb8e4f15ef8ef18b2d9e5d089afa85abb1d15822, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 061f0d25098acd02a7aedb593299b78f38f6f09b6ffd664df096a35012082269
- TakerPaymentSent · TakerPaymentReceived: 6f650600e9f65bdf60ad59b71b1657fe7a28019ca2567519d30fd137bd73c1df
- TakerPaymentSpent: ad858545daa75c628841a4e56009edfffc546ff11c2f9a40d7725b0c55103166
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.