why2 reasons
mandatedestination_not_allowed
op 0 pays GCD6R63NHD5SNS6QT7FUUHAJRLEINWMHAE7GWKN73WRX5NYQD4JS2GDR, which is not in the allowlist
counterpartycounterparty_denied
GCD6R63NHD5SNS6QT7FUUHAJRLEINWMHAE7GWKN73WRX5NYQD4JS2GDR 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
- e9ddb07f9f5a0a18f44b45b4d327beac7d9344eb7ea2b7d927fac6ac6df42ae1
- request
- 920211b5e9ed14fe5d3c8d7cde549715c6d2a1f2228d715d8c0e5fde695440ac
- transaction
- 351b924d06296abd188305230d65b9b67029fd2b78639f5c4d39beb95a62a765computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12313
the chainentry 12313
- sealed to the entry before
- 18a1413b08535cd57c025073d54a0a3be31d6043404e252f0a73827e2ca20045
- this leaf
- b2a3b47d746d676f50f1456bba08cc8c2c6f5cd09b25d504b2a5c0e4348c5689
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0Eo0e1Duoetzs6UDrObRUJ/gNLdxnY8pRmuqFEINgzbT3hu9tgE4QKW3zZUyCU58mEqel5QOina/UWk56ZsaDQ==