nexo FAST calls it the Terminal Configuration Data: a stack of tables, one per subject. Each top-level block in the file – e2, eb, f0… – is one of those tables, and inside them the same DFxx tag does not mean the same thing from one table to the next. This tool resolves every field within its own block, cites the section it comes from, and decodes the ones that carry a bit table.
File format read: sepaConfig (XML).
You do not have the file, only a value: someone sent it to you in a ticket, or you are reading it off a parameter screen. Search for the field by the name it carries in the XML, or by its tag, and paste the value. For a lone tag pulled out of a transaction trace, the other tool is the one you want: the EMV Parser and its “decode a single tag” mode.