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 MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried while the timelock holds.
the transaction was rejected by network rules. 16: old-consensus-branch-id (Expected 37a5165b, found 5437f330)
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 shows the maker's payment still sitting in its contract: neither claimed nor refunded. The maker had already collected the taker's payment by this step, so the taker paid and has not received the maker's coin; the maker can take it back after the timelock. Checked 2026-09-22 15:46:19 UTC. It will be asked again.
da28897138d49a3de361cd40f781a4ecbd70d8751a9a1c9439f6922b6e410379
Both payments are on their chains and locked to the same secret hash b373ac4e8e038cb878e7547fc7a75fe070f31635, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · da28897138d49a3de361cd40f781a4ecbd70d8751a9a1c9439f6922b6e410379
a82ef4f800d6979ffffd730f8df6c25722aebcc503ba45c343915999548adbca
Both payments are on their chains and locked to the same secret hash b373ac4e8e038cb878e7547fc7a75fe070f31635, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · ff3283362fcf6b435afa1bd6db0542ab9adedd165eab9bcf34d2ed64e38e66ac
- TakerPaymentReceived · a82ef4f800d6979ffffd730f8df6c25722aebcc503ba45c343915999548adbca
- TakerPaymentSpent · f249e4bcdfd35b2edd7cd2e8cf6e72e51edfcee20b6e14aacd06e37d740ec409
No anomalies were recorded against this swap.
Reported by defistats-gleec.