why2 reasons
mandatedestination_not_allowed
op 0 pays GDSSD3PEJVGO6HCZUFVK5LLOASRGHTMWVUN5RQIO3KYH5ADZYD5YV3BG, which is not in the allowlist
counterpartycounterparty_denied
GDSSD3PEJVGO6HCZUFVK5LLOASRGHTMWVUN5RQIO3KYH5ADZYD5YV3BG 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
- 21bd72aa6a9abcfe6f7317c5339423a2d1c6751c73997048099e3772e0c304cf
- request
- 07a2dc6d27e2b543aa122e8c51f148a5589427c499f11efa3a94a88baf783c95
- transaction
- 33e8204473492b94d353847ae6160d13910f8b70086cdc39a42fd4d33018bd26computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68453
the chainentry 68453
- sealed to the entry before
- dd2458454789553c037aa678ec0a00bd20c63628e092057531d6cbbb62fdf67d
- this leaf
- 2096d666dc0695cb3f66791f4e9959bf52a4bbde3f69df5934e2bc4aed31f8b9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FqM5DuUhTyUHYXaSI5y9lB7bOEQ0Xu8mBw2lr4kZOTqpDx+PxJ0H0vG+XvqFWurcN3VKSuWocRQo1CBZIUNdBw==