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.
8174e3ec7ce7de4eed3535b8c44c2e4a049966080f3f590a1127265835738959
Both payments are on their chains and locked to the same secret hash 02f7cb6ae39350d00d2898bf1337e87b66d4e4fa, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 8174e3ec7ce7de4eed3535b8c44c2e4a049966080f3f590a1127265835738959
- MakerPaymentReceived · 8174e3ec7ce7de4eed3535b8c44c2e4a049966080f3f590a1127265835738959
- MakerPaymentSpent · 18d6c52f5f82ee35f68d09c93bc1adaa5f5d8dc3fe59e622012aee4ef1ae80d9
05fbb971c3f997c4d9cf79d1003123cad431ff96e72e863827341671766ca7a8
Both payments are on their chains and locked to the same secret hash 02f7cb6ae39350d00d2898bf1337e87b66d4e4fa, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · f7fb510a3d915974cdcabbcbeffb711226618cbef44f1a91d3ecedfd962e2519
- TakerPaymentReceived · 05fbb971c3f997c4d9cf79d1003123cad431ff96e72e863827341671766ca7a8
- TakerPaymentSpent · 194025fd3cdbde15fcc28560009a05bd8120ff5dd19cf20452786bf101902eb6
- TakerFeeSent · f7fb510a3d915974cdcabbcbeffb711226618cbef44f1a91d3ecedfd962e2519
- TakerPaymentSent · 05fbb971c3f997c4d9cf79d1003123cad431ff96e72e863827341671766ca7a8
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.