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.
1c21289f821643039dcc91b2dd23cdb44fe2e1fef704b14ab4d8538be0429ef2
Both payments are on their chains and locked to the same secret hash 3a085f8c3544d7bc73c3e4e8c97311c69ce86e84, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1c21289f821643039dcc91b2dd23cdb44fe2e1fef704b14ab4d8538be0429ef2
- MakerPaymentSpent: e8209d4bfca0695f6b40f11fbb3f5e834b70c6a3c11aff77f68b19b08d1fe2e7
aba9a1e4051f024e23548851dbb05c303a8f36e1b8f2c3bb89d33adf81724962
Both payments are on their chains and locked to the same secret hash 3a085f8c3544d7bc73c3e4e8c97311c69ce86e84, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: acfe5e11c95905dfb6cd720fde463fc333d7af48c6a706b2cc88e0df10ded28b
- TakerPaymentSent · TakerPaymentReceived: aba9a1e4051f024e23548851dbb05c303a8f36e1b8f2c3bb89d33adf81724962
- TakerPaymentSpent: 91237c089a6f8c9f689ca0cd5eef44865635bda4deb6abf999bf8615dd1ec306
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.