why1 reason
spend_windowspend_window_exceeded
this would take GAJQODNUXMC6PBSZPNG43XQYH6QNTHTKX6XG4GS4IVLRBU4LYDZV7ZMH to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- cf70f582e155a0fa0e2c18b35014a761d6e37547e6dd2217a48957b5e03d0c84
- request
- db35b9da11957be55b195ff0c3f5d9e48e2716b9e11f1c00452ca133601e0ad5
- transaction
- c8826329b4dd57f669e65c8ce86dbce09c0ae7f00505eeb395cd7c5704774357computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34457
the chainentry 34457
- sealed to the entry before
- ca65901ca7d3cbc67d4120bf9fd0f4d0cfb1f0ad9420e357ceb77442b2b14e00
- this leaf
- bba9b0278ea051562fd59ffbc8a2ec2cb3cf02a7173915a35f5711f13549bd6f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YPMra+RO84DrsAmqCQiZ1XO4eeMXDZQGIFtaKFQoxbDhuGwgspTsZRmQd2IYZIx00bi9MU/LVbC8ozBtkInmAg==