why2 reasons
mandatedestination_not_allowed
op 0 pays GDGZE3IRSBAOWNIYMSM5UZLQLQ44MUQ5LPSD3VHKYGBQPJSVTJ6GKI6G, which is not in the allowlist
counterpartycounterparty_denied
GDGZE3IRSBAOWNIYMSM5UZLQLQ44MUQ5LPSD3VHKYGBQPJSVTJ6GKI6G 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
- 0f95ac57ee0c21463457855fb802ab973a2c2db574e3fc971c5ff1cf3c0717e7
- request
- 2e382bfd2a4a3bc98b64201ecd736b11aac6d582afcf2b9433f2685ac7cbbe81
- transaction
- 7735f940902931eca723113fc195bf5cbf0d357e372bcbb9e573ebaf5329e00acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5553
the chainentry 5553
- sealed to the entry before
- f690f0842a46c1c9851e510e07721083cd9982848ffd191bad6df992a71ea10e
- this leaf
- bc6c196205e8a8ba7ce7850ddff584aef6511f043dfb1d28bf8c67786a084176
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gvhnRhI5nxHMMxDeoa6ibsXk7kzG8m7EJiLBdqSQoB90UaOf7zhA47zj6BZ8QbKE4TzgrtgZZ0/fA3aZDBhGAw==