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.
57ff4fc46d9136816c15e1b77e0fe29a6eadebb9e830338826c3aaa67353143a
Both payments are on their chains and locked to the same secret hash 3c0ddf442a2f3271f5e49c8cbd8ad31f722c38a5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 57ff4fc46d9136816c15e1b77e0fe29a6eadebb9e830338826c3aaa67353143a
- MakerPaymentSpent: fd71b52b2cd3a03df3af673bfd4f784d012788bddc6ba69dd746c03c2291adce
63ad1c1b0e0302c5eac1b2481a47038c4c1a1af69ae0bdbcf86843e8b8fa58a1
Both payments are on their chains and locked to the same secret hash 3c0ddf442a2f3271f5e49c8cbd8ad31f722c38a5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 35cec6dc4e41ac29e1d913580ca000dbe1b312008085341e40951215d2604b7f
- TakerPaymentSent · TakerPaymentReceived: 63ad1c1b0e0302c5eac1b2481a47038c4c1a1af69ae0bdbcf86843e8b8fa58a1
- TakerPaymentSpent: 86bf43416e45fc6ea5a97f7aaa4ac42603a7f57e702e232cfb6a7b7abf4f3fd0
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.