FIRO/RXD · swap

1a9e1459-edf4-44f5-9931-b6d578e4bb67

Sell · 2026-04-02 03:11:40 UTC ·

What was traded
Price5,819 RXD
FIRO amount0.5
RXD amount2,910
≈ USD$0.2647
outside the lookback window
How long it took
Started2026-04-02 03:11:40 UTC
Finished2026-04-02 03:23:12 UTC
Took11m 31s

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 final claim did not go through on the first attempt

The record stops at MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried for as long as that payment is unspent.

the transaction was rejected by network rules. mandatory-script-verify-flag-failed (Signature must be zero for failed CHECK(MULTI)SIG operation) (code 16)

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 still be made for as long as the payment is unspent, and since the timelock has passed the payer can take it back as well, so whichever lands first settles it. Whether it was retried 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 secret is public, so the taker's claim can still be made; the timelock expired 2026-04-02 07:31:40 UTC, so the maker can take it back now. Checked 2026-11-16 03:23:20 UTC. It will be asked again.

Wondering whether this one is yours? SwapScope cannot tell you: the parties are salted hashes, so that nobody can test a key against this data, and that cuts both ways. Search this swap's uuid in your own wallet's swap history, or open the payment transaction above on a block explorer and see whether the address paying into it is one of yours.

On-chain evidence
✓✓✓maker leg · RXDfrom the swap record

1b6ad73c60390bdd89e63515857f7d6b696924b78a9d0d3ecd5a8f5103a37da3

Both payments are on their chains and locked to the same secret hash f11645130e414dc649de970b37dfe9c3985666b2, and a preimage hashing to it was published on chain when one side claimed.

  • MakerPaymentSent · MakerPaymentReceived: 1b6ad73c60390bdd89e63515857f7d6b696924b78a9d0d3ecd5a8f5103a37da3
✓✓✓taker leg · FIROfrom the swap record

14adcca71b6784010c8a491e2b4f9272db3daddcd740fc3556bc7ce229bc02d8

Both payments are on their chains and locked to the same secret hash f11645130e414dc649de970b37dfe9c3985666b2, and a preimage hashing to it was published on chain when one side claimed.

  • TakerFeeSent · TakerFeeValidated: 792bfc54edb9c8066094a965e84ad76b83b5f619e2c39923fa18a09b1c58989e
  • TakerPaymentSent · TakerPaymentReceived: 14adcca71b6784010c8a491e2b4f9272db3daddcd740fc3556bc7ce229bc02d8
  • TakerPaymentSpent: 6dd76ed48fcb17fdb49e224413174075af6e708a923256d2d85065e0d5061b2d
Who traded
7cca7b82
Taker4a9ec7d5
Maker clientmympm
Taker client
Versions2.6.0-beta_a12695e · 2.6.0-beta_5308356b5
Flags

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 defistats-gleec.