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.
68e3af613536a82762f43dbcb3231091ef6a4c52b5b84a9b058057f92ed5720a
Both payments are on their chains and locked to the same secret hash 73e3072b8f3a2e0e909a80a79ce6e7159cce1405, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 68e3af613536a82762f43dbcb3231091ef6a4c52b5b84a9b058057f92ed5720a
- MakerPaymentSpent: 4bf434ab789a5dfff27661ab9a97812c634a0fe89b53d53c98a4cecf52da089a
8b95a5b71dfdc6d09c8670073e5e4da8a290b4a60480db850f65b93c9fefef3f
Both payments are on their chains and locked to the same secret hash 73e3072b8f3a2e0e909a80a79ce6e7159cce1405, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7a562abdaed8ec48af1f0d5ca8ac7fb60acd6b078616ae61a205bba853baa7b2
- TakerPaymentSent · TakerPaymentReceived: 8b95a5b71dfdc6d09c8670073e5e4da8a290b4a60480db850f65b93c9fefef3f
- TakerPaymentSpent: 0717eb336cb8b643f74185aff24ae541182073cc59f2d217b18fe2579da5cb6f
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.