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.
3526230eed90ee39500a8a9946095c30825645d8d9ba89870a1406fbd0047b81
Both payments are on their chains and locked to the same secret hash e78e659da8cda2fc06ddc27f1d6222d26737957f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3526230eed90ee39500a8a9946095c30825645d8d9ba89870a1406fbd0047b81
- MakerPaymentSpent: 718ddf918191563c6436377a4b9072095ccece80dba85035cc26644b31eb85f4
d2d879c9a5e6147635f14744a28dfa75964f6d78dca791a8ccf6858c18638a77
Both payments are on their chains and locked to the same secret hash e78e659da8cda2fc06ddc27f1d6222d26737957f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2f50eeed1422c77ef544ba62c12a2aa926b8e4df108443f9e1b5b73f1b5993ff
- TakerPaymentSent · TakerPaymentReceived: d2d879c9a5e6147635f14744a28dfa75964f6d78dca791a8ccf6858c18638a77
- TakerPaymentSpent: 6fc2c558bf1db95d96451e2ea39bba1c47354a230bd7f43c4a510f5b7476d0c6
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.