why2 reasons
mandatedestination_not_allowed
op 0 pays GBXGVPKF5WDQ5FQNMCPC3B2HYW3OYICP5QQEBGWQGMIZHZYGEFNYUW3R, which is not in the allowlist
counterpartycounterparty_denied
GBXGVPKF5WDQ5FQNMCPC3B2HYW3OYICP5QQEBGWQGMIZHZYGEFNYUW3R 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
- b633c73be11e546cd72751d838b5b65ac0e0db8e59d539f35e2f7c08620d731d
- request
- 2cd0360b87c6f6762fb2bbcbc3d1f82ac52657167c47f6402e6719669af3882a
- transaction
- 1e71a723f44db3c2e18bb4612b9e3be49e09c5385ace03d572f7e8f40141801fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17946
the chainentry 17946
- sealed to the entry before
- 0cd158bd31a2ae43f860dda4af955f58aeb592222402ad1c3659c037cfe6d080
- this leaf
- 6b888b2b7d7db867a18ba21c64b46a76f98a1feffed1370dfa460085edbb675f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /1aVU9gA2eKZW7hl7I/VqxVBXBihV7BwcKQOo+mo+E9huDK0szNK6vr/av8lhTjkxVuU9hUayqUtkeNZ4xKjAA==