why1 reason
spend_windowspend_window_exceeded
this would take GDQFVM3KHS6T7ECBCIKHH32SPKQEWK7KL2JSI32KDUXO5GJS6A5HGVAG to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- f0f5ca268f01beceb747825a5b721d0e6eeb7f693801d22858ed6fbb39664475
- request
- 83316bbd796b41cb10d46378105315c2adf1472b6b02b837fcf68b622c9e9cdc
- transaction
- 243328bd19c88c1239756450c83201d9ff4f70b38ce6d5658e7dde5e0d575030computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43875
the chainentry 43875
- sealed to the entry before
- 1d6166cd0a244aa1d3b954d54051adef7dfcf1f5ba5ca1af204ef5b3eaf1adb3
- this leaf
- e1b45ee7db364d1964cb1b730f26a9ff07bda89bd2beb1615f43f3cdb7443a56
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iNFamDJxzZMbU2JMbVV8kTGDauEuOPgGsCXf1gKiZNFVJhLL3LBQUlxEDaYvzIcuTDzxtzoIabzcmGi6PK6IBw==