why1 reason
spend_windowspend_window_exceeded
this would take GDLFUWHMHFEQKNQODH7JKV7RM7OZXOIHO2R6A5VB5SVMA34P4ROBZTXP to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- a4b1d787adcb09855f189dcb535d135042603b7bdcf61d487d1ab528160e4e41
- request
- efc8d6456fe192ec6a5eaa982c4a2e9ed6b6a833b37ebfdd46d0e8f9fe152218
- transaction
- 586f6f4e841c77d6d7330cc7add360f62f621955c2f574a00970a77dc04321f3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30800
the chainentry 30800
- sealed to the entry before
- 69d59676e5628bff4ca53edfbf0684d256ccc3914fe09474969b5029d83c9231
- this leaf
- 0d49226ec31d06ecc7e6ecc6834171bd86fcab076ac9f7325dece5b68cf105f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QRvJg0wr3HlJj7IfThHdwIL7CWcpaPHf6L7d60lAQBFG1TX3lekoIFBEHzggJUZmQTKzl5hygphkN4eZ8aYhCw==