why2 reasons
mandatedestination_not_allowed
op 0 pays GDNZDXTMU4LYMU7QNV64KRVW52NK7DCUBPLWWEAP4GXXVDMXPNKZPI24, which is not in the allowlist
counterpartycounterparty_denied
GDNZDXTMU4LYMU7QNV64KRVW52NK7DCUBPLWWEAP4GXXVDMXPNKZPI24 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
- 03a72ae73250081e2a3cfa0dcf19ea4076ce098f8d8dc1aa8ce2b78b3e895bcf
- request
- 4f902ca05658ed2eca3b23d86911beb3db1187f07809840e1cc87a3101b39c16
- transaction
- 0baa540fb02cfe840aebb3ec05af33dd2c2eff14e67d6f8620bd5adf1fd74354computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59967
the chainentry 59967
- sealed to the entry before
- 5ab8d2c493405175d6133b12d0317d01c573f6e932aed22bae2b9ca2d3485363
- this leaf
- f33bc81d1d5ae1f41e20136321626f9f00b0e33bfba669a365f2ffb91f5f31ca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aTuoKO0vhotlWl6cyU+dlpwRjM15029ovU/kwda92aTT2RI00zPkbq9mrUjFNllWOlFvO/wPKHa0U/LTgZpTCg==