why2 reasons
mandatedestination_not_allowed
op 0 pays GBTYM4BHVWZ46O4D76LAS4OSB3PY7M6Z6WC7YYIZPOMK3XFKNCHQOQKJ, which is not in the allowlist
counterpartycounterparty_denied
GBTYM4BHVWZ46O4D76LAS4OSB3PY7M6Z6WC7YYIZPOMK3XFKNCHQOQKJ 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
- 576b20aee11bdb2bd035006c25c454e1956834d5d0c008effdb62bc80f1d173f
- request
- 65f8b3d9c5b6d8f306b8adb306d9535bf80165c88acb27b86ce0b602c7a344e2
- transaction
- 4151100c9a42f0ea2e0681f768a29390e12dbfc1988a87f2aa11fae9512d9a9dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74383
the chainentry 74383
- sealed to the entry before
- 73628dfc85de70513f6c781aa702db1f4dcffe5afddad8fe75041a9975216b9c
- this leaf
- b4441668da1cf7ad33fac0440ed1adc92d4050c3d666ae21d9997578d3a69303
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qlrKbi6H6NdA73eQXWHY5Am9UorGxVU3sQf1E2uckjxGb72x9XXDHzx/eUvrbE8iebEQt5944vlKiZFt1lSpCg==