why2 reasons
mandatedestination_not_allowed
op 0 pays GDNE3H6A6URJDOQ5UYV52TZ24LHKEEPZ5GURYSWW2CF4ZYRRP74NFRMN, which is not in the allowlist
counterpartycounterparty_denied
GDNE3H6A6URJDOQ5UYV52TZ24LHKEEPZ5GURYSWW2CF4ZYRRP74NFRMN 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
- 38b1e23972ed97d8eff908853f9c9ea3954ae3d36cb5fbced69c8a06748963ca
- request
- 78ef0eb572427fb5cd516ecf3952a969187b6750af3d45281385404114b73b65
- transaction
- f207822b5c28af1be9aeb31e4e0e832721474a4908b0207775ec2c7ffaa7dc0dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10852
the chainentry 10852
- sealed to the entry before
- 4873b6498cc7580e1e4c1696a7ebb140093e4c2c2e3d1561df429374e02b98d9
- this leaf
- c4eae9ca9c73162a13910c1a28e8160f516979609846c349ec07331e61ba67b1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wLhDu0OwGkaQ0M7BoxemW/zM+mRRrPqZaTznfZEAFiMm7yPWUNR/SYOpiHIVbrQvclIfn+b1GOOFMQmjKowOAg==