why2 reasons
mandatedestination_not_allowed
op 0 pays GDICICVWSZQN2HSSV3U3PD3ZLR7NV2R6I6WNGVBM2NSEJD5BZPFUFARS, which is not in the allowlist
counterpartycounterparty_denied
GDICICVWSZQN2HSSV3U3PD3ZLR7NV2R6I6WNGVBM2NSEJD5BZPFUFARS 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
- d7cb062463e5f3c24c1c35979d777004b7b0a02db7332d95ec1a7e1deb5edc3a
- request
- 62516dee45c0904bb0e494cc7ef17ee9982d7ad4c61677706131f8fa9fc2f41a
- transaction
- f9fc93266462ade9c28a2df83de0ef3360bf40ede50206a22c18f5988b4acb29computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32070
the chainentry 32070
- sealed to the entry before
- db4744948f1fdcae99812bd596bba4e15603bd5cd2bb1dc18ba13bfbef7cf07c
- this leaf
- 489c3f8c49d0003ddf11e223881163779f7150a6771ed7bcb8d329e4a578cf1b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- p30WTlov8+3TFmfw+564RZuq9oFxY00Bzjr0PwatqUtOj3H8TtRATDzEiXu/dZnEm0QnnrFDch6ME3ZPpKoJCQ==