why2 reasons
mandatedestination_not_allowed
op 0 pays GCPNSJTZ7VMFFURY7EUJXZXETYRQGTXM4TLR2FBTKNP3RWGJBGNQZ66Q, which is not in the allowlist
counterpartycounterparty_denied
GCPNSJTZ7VMFFURY7EUJXZXETYRQGTXM4TLR2FBTKNP3RWGJBGNQZ66Q 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
- fc2f367c70d6fc4375dfb9145fbb1aaa265f42582b35a192feeddd7f832a208f
- request
- 92d4dc34cebccaa0d65f0e2d6851279c823b0a61462dddcf6c4d31444f064820
- transaction
- 1f1dce8540316edcf440fcd6e2f2cacd038e25404313af5e41b7f5ba87205236computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76970
the chainentry 76970
- sealed to the entry before
- c963e7577ae177e06833adbf2029f5832035d1586a3a2186969e74a3ee21a792
- this leaf
- 3d8a7616687cb786f8161360e753f097bdfdf5edf948e807b4ee4e59a719ac0e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CaeuCEcCVoPAEOqjpeHBrmdnuXXNemXuq5FHthT1Y0hsGe6FSi+WDz0uupeUWoKlh6Fj7zg6D+PzNHrD2G4mCg==