why2 reasons
mandatedestination_not_allowed
op 0 pays GDUC6QBZZ6EGWHG3MYBFOZ3X3NDIX7GRJGOFSP243PWSKVUC4A4HERG3, which is not in the allowlist
counterpartycounterparty_denied
GDUC6QBZZ6EGWHG3MYBFOZ3X3NDIX7GRJGOFSP243PWSKVUC4A4HERG3 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
- ac9e81c3d41ac5f387de6b4485dca81f5138922dc575ff880e1f06d7bb4be96b
- request
- 514bf41dc8a7e1714a11d05ebba264500a71e78159eb568ecff2fc5a3919dca4
- transaction
- fc00e8e0db20255298db9902318f0a6fe39af21bba71de94ff9acb4a5bac9c4ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72717
the chainentry 72717
- sealed to the entry before
- d45a39f699a5aba36c093866f7f6d4497894f74863cc85e7d49e7b448823cd30
- this leaf
- 2887284dcacfb8570afbf04b04d4eb4ede74ad0330f4dbcd9d5257b7a72be9b8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UBkvGccNviyEED/RCWRzYBn/IcDg8kov1yAB6IhChke8tFOMRmIq3dNKkuczulFBUM7IX3swIABrbUTVB1eTCQ==