why1 reason
spend_windowspend_window_exceeded
this would take GDMFM5NAOSHGDDUQJLDN477NHBLD6CMG5EHVJ3DJU4IYXJEEF6AVFCHX to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- da1aa2717652478eb9f829b08fc556fe5c17af969704be8cfa274703e4b0d261
- request
- a0ce62026c9d1043bff4cf78350800a4fe978a3e75dd780b2d776080cfd4b3f3
- transaction
- 38bd0c587e2c0f59de864acb94c4582d6b31a8bdf52036492ebe46950abd3aabcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7126
the chainentry 7126
- sealed to the entry before
- 040ec32766633448a7bfbb135e4583e27790c4c65536601b1fb06ac5f567161b
- this leaf
- dbdfa218cdba865a5ac86dac3acbd3c9d4acf1530f4947d77126677053633959
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K38aqceKDNA3LDiwgku7fu2fW/0V6WLC8ruuPz2O38eHXCoxMHNJO+WEChAg0KOY/Il3tM0psCnDtcDkgK5hDQ==