why1 reason
spend_windowspend_window_exceeded
this would take GC5CKGYTDZZY4J4J6AYTNLKW3ZHBE5RJCILYZKGR4UCLE6PQ3CCHSGUB to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 08d7f1f74e34a9267f12bfb73b9df283fae9e9d590d29287d2faf7da8360ce66
- request
- d2b6f3c14868cf10e9a76f32be7c4cf72a8a82567655d452076afb0e368da394
- transaction
- e5757d9f00533b57b81ac31fb172f915b25af61fb12289d8d8118c1fc041242acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30781
the chainentry 30781
- sealed to the entry before
- 8710d58a704ad564187b84c6dca1b6717f2af1eb904be821f934f2ed6751d140
- this leaf
- a8aadf3beca53af80fcaf116dd9b09f10806f015df0abf032ea484f3b46776fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z6yyFUgUJ2CXTLlHjZMXnV4m02w8C/HFiBepTdmR4aSdv/+NJf9XyOS4XySFzeyLmsZ0RQgCGf5K+CCgOTsmDA==