why2 reasons
mandatedestination_not_allowed
op 0 pays GDTO3WUUECICUHPOR2CV4BID5UJKHKRFKZY4ZNYH5URR5HTWFMLNBH5X, which is not in the allowlist
counterpartycounterparty_denied
GDTO3WUUECICUHPOR2CV4BID5UJKHKRFKZY4ZNYH5URR5HTWFMLNBH5X 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
- ed6e3338f91cbfe2f340ee5e08174e46f8f644bd38fae1d37a38de6f5010283d
- request
- e4e6da32a044ab82832a114d212c8886791e200294c195dcab22d5c123dbf8aa
- transaction
- 917448fb6ec8308255f4158408e369187321a36ec1da0f0d9a29b7a79813ae09computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37347
the chainentry 37347
- sealed to the entry before
- 292fc2e448f5060df06c016daef5ae7aadd97ed436a02174e042dd7bf68188c6
- this leaf
- d36d5221f34b5e7ce4f01dce4961a1cd3c7a8bbef03ebdb20e1832787ca6979c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zI9d5wu9FVLc5XvcI2aqjxci7/MkPM6CP/w2E+OH6i5V/46SfyAKY0UmdaJdwC0pyyw7E9su5WE1oYh4QAn1Ag==