why2 reasons
mandatedestination_not_allowed
op 0 pays GBB2PRBOYEJGZUVQMQMYCM2MAJLEQDXR6NQ44NILG7HQER5TO3VZKLW3, which is not in the allowlist
counterpartycounterparty_denied
GBB2PRBOYEJGZUVQMQMYCM2MAJLEQDXR6NQ44NILG7HQER5TO3VZKLW3 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
- c6ca54d1f0d71b39b1cd0aa5535a05f614d536934fa15fe60518ba7ce28e4802
- request
- 89b8071c05aec2cde37165bc92378410227cf32c9282ec0d498e6a395cca62e2
- transaction
- 2c5fe114b0b185cab24baca1c968472af30bfb9c6ae74258d95c59bc021d060dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33756
the chainentry 33756
- sealed to the entry before
- e358013e9b3b8aeb8981c75c0b3d1447886a8413affc4946d7eabb60152db5ed
- this leaf
- 7b80400f4a4896f1dc783d2172a8e56df0192b281c09e481950070e08110365e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qh1Da51WNhUszFWQLUjhxPSQLmGvauxs2zr0zcg7NNUHIr5Sz+4vqHIQoEUAU49ZtGE4BbJG0v+Mm9KjjoAoBA==