why2 reasons
mandatedestination_not_allowed
op 0 pays GDQCEUDSWWINX2JKS4XYD4YECXZQ2TOM2YP6YHT5U7UKF3XW2RQFQOF6, which is not in the allowlist
counterpartycounterparty_denied
GDQCEUDSWWINX2JKS4XYD4YECXZQ2TOM2YP6YHT5U7UKF3XW2RQFQOF6 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
- 01f6cf65053a8e3b9af333d5ef9522205cd9d9eadbe83b6f52556522e67aed79
- request
- 7988f37b3b7d4e30250a098caf09d9554f73211a4eab96f30f6cbc3942a85201
- transaction
- 2a1ab0b08a040802406d67b5c4e55b445cd22974e451f04577e06d7126b9a5bdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25278
the chainentry 25278
- sealed to the entry before
- 9aa17014e188e4f6795e5e11c686a0293184ad56c85c091256a6bb39237fa9c4
- this leaf
- ba8302a0c2feca7490e0c657a4fdd2c1fc9cdb1535d2fad78487f37e86e99f3c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fV+itM0LU9JR82KJhIEq/DJbeOOOt5sgcBF/ZuXLlKLRFhYlGIgevBakmjKl/7+LFiH9q2f8LC0+NwBH5+aRCg==