why2 reasons
mandatedestination_not_allowed
op 0 pays GDAXKFOTEVUJ7BJUV3RTBDCMF6YCAMVNVFM2G2ZPFUZ7VA3TWDQU6CD3, which is not in the allowlist
counterpartycounterparty_denied
GDAXKFOTEVUJ7BJUV3RTBDCMF6YCAMVNVFM2G2ZPFUZ7VA3TWDQU6CD3 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
- 4c87dd1b8cd2980276f8769101f5578013317675c0ade7211784c37c7a9a67e9
- request
- e9605d90effd034a60b8d4bba15947e4c2db054aa075e12e2ee9d9a6c32ae213
- transaction
- a95f2f242b342962f801e33ec5e98da9ef1e4fc3036781a6875abbc3818d672ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41520
the chainentry 41520
- sealed to the entry before
- 9817d6e8fd49cdaca38d2707927b9f4e3cf6b9fc2c97cce003811c397eb98ae2
- this leaf
- c4301f355c5adae5dfc89496ad5d312a51ab9943670caf00da8828cd5a43fbdd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F1DZnhEW9iLoQWJeEL18k1aEOlY3hK7Gt1ITnWHLWtb9jSajNraNM4CNN9p82wu/TXWQ9co8fpy6PN4cZlkGDA==