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.
5f8f4feadf2404b1d104810dc5d0b61efb40c91025f58ec0a84837391da23b8b
Both payments are on their chains and locked to the same secret hash 706beba972eef3b6246ddae9bc461cb5afaf2e87, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 5f8f4feadf2404b1d104810dc5d0b61efb40c91025f58ec0a84837391da23b8b
- MakerPaymentReceived · 5f8f4feadf2404b1d104810dc5d0b61efb40c91025f58ec0a84837391da23b8b
- MakerPaymentSpent · 41d95a2b3aaa8e2646f28a167fdd24bca7d1327a5bda8db11b23ac55da8a5c23
02e2298f902239395c02dffbb83bf9c393964e6921744603f356235c58d92a02
Both payments are on their chains and locked to the same secret hash 706beba972eef3b6246ddae9bc461cb5afaf2e87, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · d26b001fd69eecaea74222e04d599305cae1b7b74aa1506aefcbd857b3d936bb
- TakerPaymentReceived · 02e2298f902239395c02dffbb83bf9c393964e6921744603f356235c58d92a02
- TakerPaymentSpent · 16c23143cd5bd9529fd88e5ad21892a327aee93a05bd351bc527d27978ceedb7
- TakerFeeSent · d26b001fd69eecaea74222e04d599305cae1b7b74aa1506aefcbd857b3d936bb
- TakerPaymentSent · 02e2298f902239395c02dffbb83bf9c393964e6921744603f356235c58d92a02
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.