why2 reasons
mandatedestination_not_allowed
op 0 pays GDXK5HJTKXSXPQ3IAHE5YB73SPUF7PIDGYGR4WTA2PKFBE4TW4O6N5HN, which is not in the allowlist
counterpartycounterparty_denied
GDXK5HJTKXSXPQ3IAHE5YB73SPUF7PIDGYGR4WTA2PKFBE4TW4O6N5HN 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
- 11bd98d4483777a540b144fd987ec35a0d81bb2821ea7bf89277ddd685d792a1
- request
- 8684be66e7926df7319cb1315a6d18197714e0b070b19f9ce2ad8f4af105ca06
- transaction
- 3636135fb84c4e76c1a07e8e14d1ede45ab933da83f43d613dd20ea4450f4d11computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55225
the chainentry 55225
- sealed to the entry before
- d0b02db23c717db618663804a8dfd4f36d898512c7c56c965654c7c279ea7b3a
- this leaf
- bb9dda28235285b219f993d7555c2a80f476d3b02b77fd480af0716502dd65fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 83BBVarn0VbXaxDqyYGpbhddBRfqJe5s7lfjDC8eIBL9ho4+X/DdVE2pnzuRYn/AJDWRPAeiOT3ry6dda0NYBQ==