why2 reasons
mandatedestination_not_allowed
op 0 pays GCH55EKZO2WPB4YZK64EBOBNXNFX43WOTIPFD5K6XV6IITBXOYBTYXY3, which is not in the allowlist
counterpartycounterparty_denied
GCH55EKZO2WPB4YZK64EBOBNXNFX43WOTIPFD5K6XV6IITBXOYBTYXY3 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
- 5dc7b01bf179b4d0b2d7bd80b910149a6bd34ceac0f7a9e8bc41bcda92b682fc
- request
- 94c47cc4d3f08c8ed7dd2784e5f4dfe16d5333fddf25e674c5069b5235d18266
- transaction
- 3680e47a4556e53d1a486f149a6c3e5bff8c6e0891a67a8422429f5c447b611dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2311
the chainentry 2311
- sealed to the entry before
- 0e7f0e2200752dc27d00fd92e7f17c162a7337a9cf5136e746d54911f919f1a8
- this leaf
- 9c9079fa24726b4e69f9303073048fd04f5247802e823efc6b4f7ecfc20002da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DnOaM1d7LlfrkaW83Zre68tV9VQiKt7DztCbA0n/X6yab5cYeauZ/8Dfg0Fq272MY+4Cky4gX/kVDaVdN7rBAw==