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.
8947132ce37d992141e9b11aafa56bcc9440fdf0938a8ce9d3fab78e6379e681
Both payments are on their chains and locked to the same secret hash 350bce6e325cc674cefa9ee0b783e5c80766f413, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 8947132ce37d992141e9b11aafa56bcc9440fdf0938a8ce9d3fab78e6379e681
- MakerPaymentReceived · 8947132ce37d992141e9b11aafa56bcc9440fdf0938a8ce9d3fab78e6379e681
- MakerPaymentSpent · 31dc640be057838ec5106028e19e787491f7cfe5b8092000db3cba1a05a7c929
64feea95f916a48813d76f49219e3b8db234ab6abf41b667f5b5d51543f6266c
Both payments are on their chains and locked to the same secret hash 350bce6e325cc674cefa9ee0b783e5c80766f413, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 47a71c4dd053f8ac2db1a761c15adde6b300d6229daf54ec528054b07749b7b7
- TakerPaymentReceived · 64feea95f916a48813d76f49219e3b8db234ab6abf41b667f5b5d51543f6266c
- TakerPaymentSpent · 5ad77d61261fc213b9345347ebe9bd0a1392545f5c1decc7d6424f5249baa106
- TakerFeeSent · 47a71c4dd053f8ac2db1a761c15adde6b300d6229daf54ec528054b07749b7b7
- TakerPaymentSent · 64feea95f916a48813d76f49219e3b8db234ab6abf41b667f5b5d51543f6266c
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.