why1 reason
spend_windowspend_window_exceeded
this would take GD7I7E72YPAHK2PPT7PM2B2BHJYS3IMHDTZHHMN4B2UOPV2GQASCY7ZS to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- e0b14a3591f478e5e1305b2f0066d9ba12a2a2e5c3cf9fd7065b64280a6a936c
- request
- 66cdcf1881e0f46280b73aeb4c364cfebf0d1be53b2a0a055afd06af48930991
- transaction
- 33b3a8d998409d0d4bcd8bb00ed583068d1ae14654ad4b07108b710e0c6bff73computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58192
the chainentry 58192
- sealed to the entry before
- a63297b8bfe1f8d6594481fa28a117cbb64befca0cdce435a55f0493fdbafa9c
- this leaf
- d84ee7e39ee1ed6faf8ba63e69b02b4cb06084ba3d48e8ed91b0a2fde4eca345
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7DqVbYWv0EEpCkG1i7L1FHmNF1QZcU1oMSobnD7DlBxto7kCq6AzYL4tqcZFvShdrDCOaXnvsgWFK0DkYz5YBg==