why1 reason
spend_windowspend_window_exceeded
this would take GD4R2K3YH3METF4TZMWKIFHV75ODKWN72JKAIPFIHVZDEYGT43ZUKNDA to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- d07d9a7096f58c87082fc72bba683e766f02addc1519cf95c77a14d2239e83ef
- request
- 336868a51e018b6d950a45c893fbae05734b2d3c3ce2850917c4dbd35131a25b
- transaction
- 30616e911c7ae520dbf234c8cf25bee1e34995a4b4c9ebc3d6fe2b1d4b03b896computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5163
the chainentry 5163
- sealed to the entry before
- ad6b7d8d44ab02d2d5083f6907c549e98ff5145db10d4c97786af1899487a757
- this leaf
- 331c8e5ea749237b837654136a52969b72a576282b9929d7151a495188bfa511
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SobnpYgPbdlZehZWW3NnJoFnVEIwUSvHWgXsRcaeAJa+Cc4nBFjBCO2DsLmX4LQF4OeTBfOmi4VfoBc2AuPeDw==