why2 reasons
mandatedestination_not_allowed
op 0 pays GBXM7ENHQQNQPA7NE5WRSYDNYI7TUWZRD4P3CO2DXOR4ZIXPCP5XOOHO, which is not in the allowlist
counterpartycounterparty_denied
GBXM7ENHQQNQPA7NE5WRSYDNYI7TUWZRD4P3CO2DXOR4ZIXPCP5XOOHO 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
- 852fac07ef23abf01be24c3ed8f527a8575856da605ad5e709b559e1d61e3c25
- request
- 1818123897068ad0d31f0e2a23c7be2f1f13f8ce65aa6c2e2434f94947a37dc9
- transaction
- b08ba9f861b07ce299730c5ff16a1fe17ea495abd78beb8004b26e32cdc0f279computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74409
the chainentry 74409
- sealed to the entry before
- 8bec7a196a137fece654e4321a1ac87437e4eabd64a907f773c24895fb23de9d
- this leaf
- 73fa231f81c18d7434e48d9ae76b4eafbee3e9d25ca1260784c6b78770747499
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KlaDzsBwf92c2FgAzuLIFQ7wzlW8P+0B1fgE95kvS/B4yELIsysC5RSDYZcG1/GgU4sHcOIkE+uKtKTRVssvDQ==