why1 reason
spend_windowspend_window_exceeded
this would take GBZXG3PHEQCT6DHSHPP35J2TRI5TXY5I5Z5Z4JNMNNOAQSZUWRFVBRZC to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 826a1119a2044b0b7835ef0bd4af120e31fb1da4948c9719de621c9b4799cb7a
- request
- 23a6efed5277bc97b5cb3722ca61ed0f4687fe10e8e9d84842b4785de9bcebe9
- transaction
- 239547e0de70b1a9b0ce3775c15581a9f43e000db6b45b5b68f13a0aa0b24d94computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42708
the chainentry 42708
- sealed to the entry before
- 89b2d228b4c18a0a5d9281a914e42bae27cb495a330655fd16879fde8ca952b0
- this leaf
- dd5b162b800c9f5f124b90c8ca38b9f36e3c5d8d56152a4c70978fa0e5175989
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /Vha11VSQlonOXJyENyCFHMUzHbG4aH7toVlwhLoxb4SMLQeWEcL6fM9mVF2ETaRf1he/DHCkVzP7IivleaJAQ==