why2 reasons
mandatedestination_not_allowed
op 0 pays GBDTKICVSZNQCLNT6TRBLLUXRMWUG5I5GK3H2V2YAKKKYXYMV46BRBXK, which is not in the allowlist
counterpartycounterparty_denied
GBDTKICVSZNQCLNT6TRBLLUXRMWUG5I5GK3H2V2YAKKKYXYMV46BRBXK 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
- dc6eb72ae65ed9dc12151bbb39db91452cb41c2aa3a0ba588d4e181b22bef09a
- request
- 84700f03f129e4a62fe3fdb5dffdac70d07e6601696bbc4ec3ea53e2a5c98ea3
- transaction
- 25db310f06d32550bbdf17230eaaf3c6519cefa8ee6e98043f5dbd1bbc69f310computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3221
the chainentry 3221
- sealed to the entry before
- fcf2b5b860f91a9aebc48f99eeef0f518a6170ab2c3aff740f90f6a955be8cb7
- this leaf
- d635f0599032488d097fcca36ad10173b0d9ca0e1c38cce90c01953412f46168
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dTU62XMi228YHEvcZ4OmOYjj37eB6fPbXsP+ELWK7utcTOG+f60g+aj4vW3pCsTAh2AEQhLBmY29uH77tbgPAQ==