why2 reasons
mandatedestination_not_allowed
op 0 pays GDHR3RRWCN74TIFX65Z3NYG2KCYJGRSLAKRQM2PMVCUWL3GY6TU6KG6G, which is not in the allowlist
counterpartycounterparty_denied
GDHR3RRWCN74TIFX65Z3NYG2KCYJGRSLAKRQM2PMVCUWL3GY6TU6KG6G 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
- 254c1c6eb4c390f41615e405bdbbee0d878e96a66a029b3e8eb9599ba4284e7f
- request
- ad106aed9137c30dc9cfdfa2666a934f0ee8ee5002243da5d24cdb520f7cc980
- transaction
- ea029d1c432fae3410fd977d3482331c28d166f79c037517c6175b4e6f210345computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29668
the chainentry 29668
- sealed to the entry before
- 8076aa3945a7103d30b908d2122fe0105697e57d53b176eca2c9273be60ff33b
- this leaf
- 72da436143683625bc340aa9c7a7312975475cda165ebb8ec101ed09c8354ada
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yCBFo7hJ5F811seXkSl/8qXtNyDdyxJp+msLCIhRasoUbO2T4jOhyTRnerTY5NGeQrlr29Cw3mdwCi/rG9sQAA==