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.
c680d4c25d98d7daedeb11264b8f3c8bc6cc50a8330ca2d2748b5c09b27bd818
Both payments are on their chains and locked to the same secret hash bb0c23bb96acbc7d9a0626f00ea45291a4737f1a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c680d4c25d98d7daedeb11264b8f3c8bc6cc50a8330ca2d2748b5c09b27bd818
- MakerPaymentSpent: 17910a213dbde14eff90afc2e2f55786e6fb26b33cd46b974692272e328a5280
471eaa42a260cda296fe4da35fb030a6c33cd3e79422726deb4db15ac2461794
Both payments are on their chains and locked to the same secret hash bb0c23bb96acbc7d9a0626f00ea45291a4737f1a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5104733aaf62cb8f7004fa9d2232fee8a684e345562bf8c5e54a7cbed97e262d
- TakerPaymentSent · TakerPaymentReceived: 471eaa42a260cda296fe4da35fb030a6c33cd3e79422726deb4db15ac2461794
- TakerPaymentSpent: 629ab3afeedf6194d88820f998ba0f635f5de3e9689a9c7ff51a889fe270e362
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.