why2 reasons
mandatedestination_not_allowed
op 0 pays GD2FKAE2TBZ3JZFG4MBCS4QM46YME22QYXVCUJWEMVDFOCLZRVHKC4LB, which is not in the allowlist
counterpartycounterparty_denied
GD2FKAE2TBZ3JZFG4MBCS4QM46YME22QYXVCUJWEMVDFOCLZRVHKC4LB 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
- 8015db94501ffbd625d8747b34f4a1e2bf0386a9b972f30d97c050aba34a9114
- request
- 828489a4d5d8346e595b2cd0f2431026517c24d2df6339bfa68a1ad1f81beac6
- transaction
- e58fea9bd56b04848b816930f477c253e1773cb893e2d201ec7b69be926d3544computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15852
the chainentry 15852
- sealed to the entry before
- a0d49724f35f68e215762a76594c280fc7899429af9fa6617eadef9285a0b064
- this leaf
- 8b701ebbe1be92f34309da544e967c846e7025f73976b1c4f77dee65ea068317
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zzcs0dzRfhxwGwLJm7Vl66u5cakTmyIgag3z7zOIO3QTRZSygmwRHdCOqAnd+XSAXZ7rNtriEVNkj0l3Nf1mCw==