why1 reason
spend_windowspend_window_exceeded
this would take GBRXMRJKFJHSSD5SRFCJ7DR3IUQAYJNYBQSH6T3ESP6CTNSC54BCTSKP to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- dc3299b398cc5bec5fd7c4efc82a4c9278583e46a458268729120f4e57c8f64b
- request
- ecc95e97e9d937d8b822edab90389bcf475ce76f3043a5f646367524e63ea5ed
- transaction
- b30278c5117f83101e75f97bf2fff55473bbdcb887cea1790d2ba62ffc11276fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46059
the chainentry 46059
- sealed to the entry before
- e30c0d142609d40dc4fb04ee463618d1ae7af51164c72697c5bd14ae1786e9b8
- this leaf
- c87dc37a045d27d652b379820e41369e2d9f0be9187858f6711d0e3acaba6031
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b7BLYT9qgP/VzLV1pWqeevPnycZ5WlB0k+TMuYKRNptPu7oyAUKQHv1LP2Ef5Pnq1GEUWidVhsJtxOuIYjt+Ag==