why2 reasons
mandatedestination_not_allowed
op 0 pays GDF5BGT3EOU4UACG77DBBLTMJ67AINNLI4PNEZAC7N4QFKP3NWL3KQ3O, which is not in the allowlist
counterpartycounterparty_denied
GDF5BGT3EOU4UACG77DBBLTMJ67AINNLI4PNEZAC7N4QFKP3NWL3KQ3O 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
- 36176f4b07e21ccb4bd2becbc4cab5b98b42726d4ef3cdf686392183bd7e8fe7
- request
- b13599dc0b31b077798035726af7114ce7a896825a7ed6cd8355f3a203612ca1
- transaction
- 820e00663fd2253f2632676fd824940c57546cef712830fd5bdca74419bc9f39computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34675
the chainentry 34675
- sealed to the entry before
- e69d42e4725c7e11311328acf9192a037ec871aa6010dde8499b5f1d25ecf3be
- this leaf
- 2852403288708e0445e2f18b663861e63da940d8c28a92b209933e63f4e1d1f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- plSbeox3EHke1ZtuOQisza0kyTSNp1+fRpxYNO+wluII6tZQM6t7XBLj3C8OahfcQ0xA0q9u4uW8i04YKvkhAg==