why2 reasons
mandatedestination_not_allowed
op 0 pays GDGDZVACWHYLSUMV46RIZROGAOPB3HNCCAQ7OKQSYFIZG2FTDTCQVN5P, which is not in the allowlist
counterpartycounterparty_denied
GDGDZVACWHYLSUMV46RIZROGAOPB3HNCCAQ7OKQSYFIZG2FTDTCQVN5P 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
- ccfc11707b31fa6e829513567dea0c584135e5f3d491fd8adbcad200e0d5b23b
- request
- 3b8a9768f116ad55b92f41ea95320c63f7ef124f2dca89cce93007edfab0712f
- transaction
- 51bbb9a53f624c394b8493143f70b3af5695623fd3937c21396dca3e83148545computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73821
the chainentry 73821
- sealed to the entry before
- 28ebe2bf1d30751624c37f72881712d04abd58d7344e2b05d9fe4dc0e34a3d9d
- this leaf
- 6912de2c83c193d50f2285735c309fd93114140e5362655a5ac6708972ca0137
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D79jp6rjzwqJQooeu9Xbywy+/bdFiHaB0wBl57Nszg6AVj7vr7zANUMeibDE0D0aroiDzl2XvGFRD9ForY4VDA==