why2 reasons
mandatedestination_not_allowed
op 0 pays GB5TUTGTOZA3HVAC2UXVIZDRH3VUIAHSYCRTENKTH55WZKH26DCDFZV5, which is not in the allowlist
counterpartycounterparty_denied
GB5TUTGTOZA3HVAC2UXVIZDRH3VUIAHSYCRTENKTH55WZKH26DCDFZV5 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
- dea1f34e29269f335a5eafc24311c69ed524e4381404109eccde62a3b99ca6e9
- request
- 67e4a3f08bb154cbe25c445589594c0ca1da5696149077a186a3d1a7ef45f145
- transaction
- 11fd1a38008dc302314d1661f2b7068f97e1930614609dfddc876ef6c71d5a92computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 912
the chainentry 912
- sealed to the entry before
- 9e7696aad79e411478c1ff9ade2ad714bd26c23bc5c99cd0aa5ab354038cb1d4
- this leaf
- 1c01032cf2e689e5c3f615f4f14ff7ca0deded6ec7584d749de3032e55211ebd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- orzgsBrEHUXXNsb9sedh6nxH7jDEb8oOYN4TnN/I8tMFARLGd7pbjiBTbGmJHW9NQmtKSgXciRlah5gb5h7vAQ==