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.
The record stops at MakerPaymentSpendConfirmFailed. The taker's claim on the maker's coin was broadcast but not seen to confirm.
taker_swap:2052] !wait for maker payment spend confirmations: eth:6127] Internal: eth:6127] Tx receipt Receipt { transaction_hash: 0x8244839ab13263600c03ddbb02d539860747bcb223ae37c442bfaa90ebdf1ed7, transaction_index: 198, block_hash: Some(0xe0e17db552ec0268f419977c9c6ad2304b5d33393c7204314decb8309…
By this step both payments were on their chains and the price had been struck, so the trade counts toward the reference price. The claim can be retried for as long as the timelock holds, and whether it was is a question for the chain rather than for this log.
The chain says the claim landed: the swap contract records the payment as spent by the receiver. Checked 2026-09-22 15:40:31 UTC.
cee2612f5e0f72913aaa7c7f695a918fec1010b8fb5d6aedefa198ff0e7e4cb5
Both payments are on their chains and locked to the same secret hash e1c727f89777aa24b875aaa301bf0b2a7a522beb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · cee2612f5e0f72913aaa7c7f695a918fec1010b8fb5d6aedefa198ff0e7e4cb5
b214ce81a1c251471fcf3224d8fb0b026d927482984543fd87be92333df30753
Both payments are on their chains and locked to the same secret hash e1c727f89777aa24b875aaa301bf0b2a7a522beb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 9ab6f78534e0fe792b6a9001b8e5a7c3c2fbb35efa21e45abe9a5fcbc9004d66
- TakerPaymentReceived · b214ce81a1c251471fcf3224d8fb0b026d927482984543fd87be92333df30753
- TakerPaymentSpent · 521e4fe76e097304426a5e15d6eba0de9c8527c6155b91d3302fcc8bc0d8c6c7
No anomalies were recorded against this swap.
Reported by defistats-gleec.