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.
373d0113008a10e2e4ad50c659d002ad6957fef44000dff28655668b726feef6
Both payments are on their chains and locked to the same secret hash ea4eff0fe931116345aa1dc8d665393315bb6825, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 373d0113008a10e2e4ad50c659d002ad6957fef44000dff28655668b726feef6
- MakerPaymentSpent: 49362146dc7f1e2e21b6ba03d854b61a8c031c418a9d31d72c9273ef3b4d6950
9acff8d09942200162e7b98b88be2b8ce51dd871d04fbcc5717e7322554226bb
Both payments are on their chains and locked to the same secret hash ea4eff0fe931116345aa1dc8d665393315bb6825, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 90a48fe904393a2f0e860a1fc10d7e868ea151541b8a4cfb4e7f19912390c144
- TakerPaymentSent · TakerPaymentReceived: 9acff8d09942200162e7b98b88be2b8ce51dd871d04fbcc5717e7322554226bb
- TakerPaymentSpent: 713f7bcbc508fd44313fc332f3257b41ba683c94f6d4193bcea1833e53ba3503
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.