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.
3851ef52f7a6f1a2a04d9b390183f0000c28786ac219f984b04113148d4abe51
Both payments are on their chains and locked to the same secret hash 5792d7e7bf8c24684f13a050f19094324b410e83, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 3851ef52f7a6f1a2a04d9b390183f0000c28786ac219f984b04113148d4abe51
- MakerPaymentReceived · 3851ef52f7a6f1a2a04d9b390183f0000c28786ac219f984b04113148d4abe51
- MakerPaymentSpent · 7e441a92ff0c1b3ae0a667e0324e0cae24687818895c532fcc7d2e1f2bdac27e
b30a74a5bfea135120d487c20ddb7dba4a8f6f50dfe4c177cdb1e938ff034719
Both payments are on their chains and locked to the same secret hash 5792d7e7bf8c24684f13a050f19094324b410e83, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · daea4d34bf92b7f2ac1d3b3e6c11c120d02d26d73e08dd00739fcd66b4fe9250
- TakerPaymentReceived · b30a74a5bfea135120d487c20ddb7dba4a8f6f50dfe4c177cdb1e938ff034719
- TakerPaymentSpent · e4360be72fdb086eb56928690f09889d4c13c1792d174ba8ef180aa8520f46a8
- TakerFeeSent · daea4d34bf92b7f2ac1d3b3e6c11c120d02d26d73e08dd00739fcd66b4fe9250
- TakerPaymentSent · b30a74a5bfea135120d487c20ddb7dba4a8f6f50dfe4c177cdb1e938ff034719
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.