why2 reasons
mandatedestination_not_allowed
op 0 pays GD35UH2GYUGRDKC6GX33W5ZGTUZYHGAQPCX7RRWX7UT7GN3P3QTNDO7E, which is not in the allowlist
counterpartycounterparty_denied
GD35UH2GYUGRDKC6GX33W5ZGTUZYHGAQPCX7RRWX7UT7GN3P3QTNDO7E 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
- 08f9c3220775cdae4fd236a5d3071aa714b21bbbf17c3ef051f41a8e4ec03590
- request
- 88933e5fd48937135a53321a35e6ce60a70b8de0b6d534c060b520c45ad06c5c
- transaction
- ea941ccf265202536147c48464ceb80b56a7e4ce61be8fe88d1ca684a15c8e77computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41449
the chainentry 41449
- sealed to the entry before
- 268d84134bec724227e9bd3a5b4bdbee8bc7233f46ea230ef7a7da03c1f52dcd
- this leaf
- 93672a0768803757b55a58bcf7e8d9fb6fad0515be83f79299deee2a87fb5ab1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DcldQ4d2vKkZBqoL430LC+nYafHvAT1BQxO4vie5SzQ18ajYB/RdW4ABwekldwimoJiOopZFuQT9j5TJWwJVDw==