why2 reasons
mandatedestination_not_allowed
op 0 pays GDIV6QXAUJP3EUU2BAUVANYBC4T6MTQ46X77VTNKX66ARUOBID4CJ6RQ, which is not in the allowlist
counterpartycounterparty_denied
GDIV6QXAUJP3EUU2BAUVANYBC4T6MTQ46X77VTNKX66ARUOBID4CJ6RQ 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
- 4b4a03431e45c4e6cde7d469bdb24b9940e613a6294314b0e31287f7f901a342
- request
- aeff3233a348c722b8d37c922331ff33fb00f0ae011e48609f59726145efe3c7
- transaction
- 8ff702f37e16b79d6f3eedf32460f87760611e25cbcc7e0602b7557ec90ef914computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45754
the chainentry 45754
- sealed to the entry before
- b14440256a8be660d06076355bd4e59d71c2fde133f5a978b631c80ac9e1c71d
- this leaf
- b12b28ce592c0d3e2462aa8e679f3e8d11840c468215d3face985d7e98dd7192
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ckUsX3KkTveSFNlagosP+MveJ9hydQQ0rP4o5cYj/ijhToOkQtO4MSM4w2Doz0RSvLRKQ+SBYmRxEirUO6KEAw==