why2 reasons
mandatedestination_not_allowed
op 0 pays GAWP4ADJSBKWH3SVUNBODOGD5HQ44EMXWGUQVMDWGLEKQY3VZ3PTO5Y5, which is not in the allowlist
counterpartycounterparty_denied
GAWP4ADJSBKWH3SVUNBODOGD5HQ44EMXWGUQVMDWGLEKQY3VZ3PTO5Y5 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
- d39742a06c54bfbde5624c51124a8e9e6904c331c2f99bd70ae628d379fbc6dd
- request
- 0fe4b3570de777e437e32d8fc8140e5567278038d205e726416360fab46abdf9
- transaction
- 399b463cce208e2ecda36e3ad532bbbb63c42b70848f05c18c2f288fad2dfdd6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66747
the chainentry 66747
- sealed to the entry before
- 0b25ccc648538dc5024bd2572f10fd99fc0e682c4929fae93e46a64da79fba39
- this leaf
- fc61d3fd93fe501b445495856aeaed917db635b6f521aa41b99f31c71d882731
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4/bH0Mzxa6PkaHdn+uabMlzYnrfXF3yBvTpPUhWEtymVC3YhIXeScCKKXUyyg4si44gxh6zeehVcNY1zXDkhAw==