why2 reasons
mandatedestination_not_allowed
op 0 pays GD7PVZLZK7LHIE2VWNCP6SVLDNORRWJ2NXKFOZR34TDIHYFFTMYVYUTE, which is not in the allowlist
counterpartycounterparty_denied
GD7PVZLZK7LHIE2VWNCP6SVLDNORRWJ2NXKFOZR34TDIHYFFTMYVYUTE 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
- 48ea88e16b526350e41da552dacd4bddc6a770339e58d0af59f748862501bd35
- request
- 71d51e7ccc5347daeb999329966c742c6155a4d79679286006c8a0f65cf64c79
- transaction
- c167845eec0e49d184418b02ebefb4f16a3a02bc1268b94fa5137cad76d58966computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53400
the chainentry 53400
- sealed to the entry before
- d4c3d518a3212470205af11dd313e01e61cd02b8685e785a3ac010835ae2f505
- this leaf
- 41434bdc2891f2ce7b380fe8f18441c9a57a59858ef9322cd87a03340b0edac0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lKVIk6tJ+8V9Z7Ez65fjtOf78vdMbsLXODLFuRMLyBTOdAhuAA8qFwMHsAbiLU1Sazim8CM1MGDjB6WIxRuxDg==