why2 reasons
mandatedestination_not_allowed
op 0 pays GDZJS4J6E7VP3NN3HKWTVVRYC4S7S2ERV3FPPBIVJLJGU65QWD6RPKNZ, which is not in the allowlist
counterpartycounterparty_denied
GDZJS4J6E7VP3NN3HKWTVVRYC4S7S2ERV3FPPBIVJLJGU65QWD6RPKNZ 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
- 95c4c55025b08177c88f2390d36e4e044b36363ece8f7143699ab1fe3e910bd1
- request
- 093416715776f8dbad3d02691a0f773f351dd7c7555fdd6c0c1141c056e218bc
- transaction
- 75fbdf14af36f3661f685a6126d9365b5ec4260636d132c516dc7627eb2a429dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74002
the chainentry 74002
- sealed to the entry before
- 5749462610fa68c51f6a9f86c467de255d7bffafc52aaf433149045afb4a06aa
- this leaf
- 1830b40603f0e01892f933721d8215f40dd2766ca96cfccdbdd555d4da0299c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4nJetTbxSaeIEBSTmKa3Ih9R9ZL3P6AWz0/T3atGz+tt40tMTYFC9OrxY3IHMyWtn7h/lcxCnoGGa0mDhSpdAw==