why1 reason
spend_windowspend_window_exceeded
this would take GCLRAO4FUNCBE2PNN6PRZESI4FPZJBU3GLYLSQSW46FGL5KEZ4BRTIW5 to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 9d5490b39775b4d6d80a72dd78ef3911406511d106a9c141afcdbd83213ad288
- request
- 8f5b05594697204efe0ad5d6f3c992268ed8a0af20f37860760ea49852de6b7a
- transaction
- 20ec891a1824d7afea51dd8f3f217184e5b6dd9e55d057726b25260096d80787computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18138
the chainentry 18138
- sealed to the entry before
- 16beebf28546e818265cd0bbc3be731892a73d69ea5d2a7775c7f60b0ed3684e
- this leaf
- c78a5fadcf03a4afcea7df6796ac7cff235082f3e3b94ed4a9c150aeef80fe6f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b+QtgutNmnAGj8dyNbMhZzCJdhJWMioxmlpGEwki6EmRKLbDjhQ74yCZB3thw6YTYhEj8lGm8VJ2+k/vxjS7Dg==