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.
f59318e3ab9a62e8df0c0837d51a0796f703ed905bc09064bfefb6a4137c33ce
Both payments are on their chains and locked to the same secret hash 7d75890d5d238325e71bb7a48a66a5fc40a793a2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f59318e3ab9a62e8df0c0837d51a0796f703ed905bc09064bfefb6a4137c33ce
- MakerPaymentSpent: 4874a6353e167fbb66f7f1d08815c5f9641a6541cddeeff6060b6b46fc930da0
1463e0ef08e5ae8278f6dd8a2b98df2c3297e61334659e5aba4181762e7fde53
Both payments are on their chains and locked to the same secret hash 7d75890d5d238325e71bb7a48a66a5fc40a793a2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c61e0bba0f03ce34ea1ce475e428e9a00d310cf2c96f1f5322dfe5ef378a3663
- TakerPaymentSent · TakerPaymentReceived: 1463e0ef08e5ae8278f6dd8a2b98df2c3297e61334659e5aba4181762e7fde53
- TakerPaymentSpent: 1a38a5ec1cc7cd49631890abf2ef2c1769eed7c76f2045e944067dcb76e65eef
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.