why2 reasons
mandatedestination_not_allowed
op 0 pays GB5DYAAHW3XAI5WZRER5GKJRZEVVGOUP3JGGD2RHOJTHT6FKR7AKB425, which is not in the allowlist
counterpartycounterparty_denied
GB5DYAAHW3XAI5WZRER5GKJRZEVVGOUP3JGGD2RHOJTHT6FKR7AKB425 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
- f3ebdb587f453b414d7e876b3ceff3beedd687bf5688846dd33fa20fe74f3908
- request
- 2ffa179ebff211bb041e54f8043c0766f2a60435dc096145e73bc0d648cc07f5
- transaction
- 5c64aabe8f50119561594afacc274bfc214a38e3291f25d0be699018ca6a23a2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60179
the chainentry 60179
- sealed to the entry before
- 6e60a6533c05bc2e1a6e0747c167a10bd18bdef7de25bf6bec17829ac655d199
- this leaf
- 19197b10d4af1cd7c636adc831fd515d08707e92677a4632122fe17780908788
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +Fmyzcu/Bi36vhvt9XADKoYVomy6+Kh9C4yElT/25MpM4cUgQEEo+yr6vjt4z07wmZa9JP1+64KpGiGlRhCDBA==