why2 reasons
mandatedestination_not_allowed
op 0 pays GD6NZQBBHBQCFU5SULMITP4VL7NAGLJOLQCKY5VDMRVJGIMNP6YABWDM, which is not in the allowlist
counterpartycounterparty_denied
GD6NZQBBHBQCFU5SULMITP4VL7NAGLJOLQCKY5VDMRVJGIMNP6YABWDM is on the screening list: you placed this account on the screening list for this run
what it was decided fromfingerprints
- rule compiled from it
- 6a5aea133e4b28f12c511e29988d1427d7a842a2ba13a871160c5748e214be72
- request
- abe90015652e4a9e8d08f53734088ddebb6ceab3552640f7731191dae9909dd4
- transaction
- da53e033feebdf778a9e2989d82e58a0329e480b9576307934ce1924f89d33c3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25028
the chainentry 25028
- sealed to the entry before
- 1b2720a81fe5119925566de8ad6827740e77b9d8319f13bc3fb06968ade6b35a
- this leaf
- 72f11fa10fe27fedd6ca26ecb227d78d3dc884a8a58a3b2bd4cea09fcf9907d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rkr75sCJ6f8eBnjSlW/ES1HUElgNNjCTLDR1tYECZ7cXvhCkpBtEQegnA8dfMQhIOxvZG2LhyhXpjKyeGVibDQ==