why2 reasons
mandatedestination_not_allowed
op 0 pays GDTN2YZZCHJAUUH757BMIHTFA5MPVCL2VAD4M5G4XM4HJH2IL3DVZPDH, which is not in the allowlist
counterpartycounterparty_denied
GDTN2YZZCHJAUUH757BMIHTFA5MPVCL2VAD4M5G4XM4HJH2IL3DVZPDH 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
- aad71bdc5685d6e747dff267b2160b81d0b041b90880be8f21584f9e1373d416
- request
- 1d1c42d9288ee06f7c156915046e0e890d71b2e9ff30b0be85dce8afe28bd58b
- transaction
- f020641f25af9e0a4b1a7531b289efeb7218c985294b250a98e9813877eee71ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52607
the chainentry 52607
- sealed to the entry before
- 871c5769e51e3328a3b93bf5fa2f9d642470275bcf153bd5500470b2e4730459
- this leaf
- 2b08d5130c9b5a8565340a91050c5f9868686149cb105847163b06ad41b9fc73
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wdbupPU46GwBedMczQYjGUqaHXeekrBx0bOUAFbeJUiUjaXV+WivNMI+z1N277GtSgtHqxiaTbNvMn1favVxCQ==