why1 reason
spend_windowspend_window_exceeded
this would take GDW7XC2ENCZYMKZDXCNBWEIKR5QCHSDY5O2G4QHYQ6IHERB4OQRZIPSH to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 009234db2ef4aa0e6ae3ea6a7fb9fe8509b5f0b8fff29a63251fc395f81e49f9
- request
- 7a4eab687c442148782d433e368f1dbcf26b0c60724751f83973cebe76400a2c
- transaction
- 1186f07db06096ad6f9b0cfbe43a5850c220abb01e4b6f89730a5b854db856a1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56870
the chainentry 56870
- sealed to the entry before
- 1feba63fbf05557e4bedeb88a1a3fff957445a1b977b6860469c13e3e168ac5a
- this leaf
- 47673b48f212077cb1b57260022308e99a4351fec4aa8b135075465f258d4763
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tgxBc35qpnrLdCFUBpPSyL8iUC+hRlyaDzS7NBUkrKUngiKOpMFZnC92tkKdYIF3Zn84jPvxIVX8gcHVIiqMBg==