why2 reasons
mandatedestination_not_allowed
op 0 pays GDPPE76IEV6PP7CWW4LB3C4V5DBLKCVQZ3QGVN2RWWHBJCLO2XLFK6PG, which is not in the allowlist
counterpartycounterparty_denied
GDPPE76IEV6PP7CWW4LB3C4V5DBLKCVQZ3QGVN2RWWHBJCLO2XLFK6PG 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
- 3205d8dfd431c603a37d2ec84e4806edba7d44fec3e6ea1112e22e5ca7b3c968
- request
- 88720f2aff9ffd444181a5e3c68ef99193084883c71ffaa904ba9d0789cb53fa
- transaction
- 94d2f883ed44766e9c4b1e923fab65fdddbdfcb5c806e15e91fb8824df356af0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54861
the chainentry 54861
- sealed to the entry before
- 00b6d92bb1eef470bd389c8470e7ee67d5251714b4ec8b29e7f31ba0e7089f3b
- this leaf
- e40d922bc0958d586c3559e9613a008521a40bbd7ce270cef8697148034dd29c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nHKPqCZz++URenvw3MPRcURmlltfyNaDwl1mQ4rIxdQqw2o5OdXpuZ6d045AlM6tXxPKyhIveWh4ZtedEE57Dw==