why2 reasons
mandatedestination_not_allowed
op 0 pays GD3DIF4Q6CSU4GBYQKAF5PHQPFFFLJKHQELQ5OCW236XVEJRTQEPBF6W, which is not in the allowlist
counterpartycounterparty_denied
GD3DIF4Q6CSU4GBYQKAF5PHQPFFFLJKHQELQ5OCW236XVEJRTQEPBF6W 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
- aaa35552e5188c732fc1bbc1db46782ab2ac26685215c6288ef2da3e1fd19928
- request
- f88a31fa8fee9273d1f9e9cf87529e9f782e3248945c950719edaaaadc53b80c
- transaction
- 0e9ad3e1a8694577eefed8ba0db41f46faf9d252bd132661fc946f9feec7dee0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45391
the chainentry 45391
- sealed to the entry before
- caec2f09bc0180c4bc1e8a151181ce0b096ed0e409bb8eef3c6f3ef6a28106d7
- this leaf
- f3ca7f4e2e46a96ddc4d5e1bed0304fd0f10e0efba5439b523b5128ecf886ddd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- P2gJSBJlllSz4ixgir9hxGlY+9wqjG2wnL0Tfzf0Qe2l8b3BpVExK4ZQKBO+EZEFeI/QBni2+QESc7vQFiNmCA==