why2 reasons
mandatedestination_not_allowed
op 0 pays GDE4CRCQLY7OOKOYB7LDL2ZD7KUJ5453F5AFTJKKM7QD3ZSIJUPRTMIO, which is not in the allowlist
counterpartycounterparty_denied
GDE4CRCQLY7OOKOYB7LDL2ZD7KUJ5453F5AFTJKKM7QD3ZSIJUPRTMIO 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
- 9a63b36359b8bd795d956c41e7dcb828596d63238f84de79094deaa5189a57a7
- request
- cfb28c14a2c0a106e603de601be9ea2849d6a023d060ced2258af54d252e2e7a
- transaction
- 0ebbcdc0a052d192b7d709144c597e65c9606c1a0f3169720a7f3385d8055d2fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52
the chainentry 52
- sealed to the entry before
- 30a5cc26ebe91794e682a16da5a6a55b1e0fa0d1ef4518f933ea24efa63c97ce
- this leaf
- 6ff2991987e3b25b4d1d293563aa933dd58f2a122dd30671b6d766bfc2fe8dc8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dy1Na/5zn2Bt3C1N+DzoASrEjooduSSKYh+KUkOZnbtjJySQ890uu5xvndawRXSgJJqSaJgnu3NGv/nK/hzhBA==