why2 reasons
mandatedestination_not_allowed
op 0 pays GBMHST4NPJ5GAUAG7IIMSN4RXCLHO3MSL54LYGISUDVISA2R25EQVNZE, which is not in the allowlist
counterpartycounterparty_denied
GBMHST4NPJ5GAUAG7IIMSN4RXCLHO3MSL54LYGISUDVISA2R25EQVNZE 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
- 8d5ba350e03d80c81176d1482c44a1c5d1e861d43d3c7fbbd6d8ae78cd4808f7
- request
- 061511bd77195d904b7c36f3ce7cf30bbf8f0f546caf07cffd854dc360efc6c5
- transaction
- ca9bcbd2106fcdaca5948b3aecd4335e1d3e3ef6e876f787ce27f6aa81a819accomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65286
the chainentry 65286
- sealed to the entry before
- adac711520ee41755748631d4148a4eda06532a6a8a11ca3161b9227561619c8
- this leaf
- faf60388d7c0230eb57dd7ed74c62e33d779eee3125a83889b6e2db1b90108cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /e/jKeyke7l0SWs7tUYyhWFT2Rwpji+Ol8NZsRC5lPOEABRwq4+eD28uchZnXSAGN9mO2R4z06jtfnOOs0b+Dw==