why2 reasons
mandatedestination_not_allowed
op 0 pays GDEQ74Z2NFDBBXZ7U4UMCKSUWZMWLK5BYG5J2SDIYJO3RUL3EELHP5TH, which is not in the allowlist
counterpartycounterparty_denied
GDEQ74Z2NFDBBXZ7U4UMCKSUWZMWLK5BYG5J2SDIYJO3RUL3EELHP5TH 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
- 8dff67a5b14f5f321caa6eef10e6005a9e7fa2871ef391e390ac68897a42820b
- request
- 6a1de50172406093af70e6993c02e8b651ce1ab35566805a7782ec78f8cd1de4
- transaction
- 0f4b23f0f83d868f300cc922d77ccaa04e79f18b761f9a86d7bf2235988342a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38588
the chainentry 38588
- sealed to the entry before
- ad2e8f2f877025a8cd8f9e42ca2d2634f536c7a17975a3382b53bd3ad32cacce
- this leaf
- a90505f20a24f9d0a48ff851067e6f1eccacf6759de8d46853d99c5209a8c42c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6QLlmVgEY9XKMZtnbzYpq+1kgCqIFDlS8eV8D/dksRPKMQuk0nKt6Uju+S/rSAHyX4viQgoEjFkQg2aV69kvBg==