why2 reasons
mandatedestination_not_allowed
op 0 pays GDLZURZJNGN4HRIEJMUBYTYX6OO2GH3SRSSUGMBK2LFSZC6OU544PY73, which is not in the allowlist
counterpartycounterparty_denied
GDLZURZJNGN4HRIEJMUBYTYX6OO2GH3SRSSUGMBK2LFSZC6OU544PY73 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
- de8b704a676591d8ef704c84486bd8228e1b732305382c3f18145a5c5b3efa33
- request
- 758e922ab9a02a01bff388cce921509da2dc37f66af2fe682de6cf8a2484f82b
- transaction
- c163243addb5bd04c781c4614451c633d35dc1643de71ad6824ecaf9c0438eefcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15220
the chainentry 15220
- sealed to the entry before
- 3bb114b8c9305e1411c78b8a30c6ef8a4a6930b7ddf569e7764a41a3cc733a8a
- this leaf
- 8874fe90a50440f2a62f40feb4ab1472a17ca7b61a4f8aeed6587475cc57fe46
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gOHsRZdDhGpkeudnEyVd/0S10GMlC77HcMFd+TcjBsikESeiYid9R07YNEqXCK4ykMbS1s5iJwmgsSK1SOEkBg==