why1 reason
spend_windowspend_window_exceeded
this would take GBIQNETOM3RB2VEBNZX3IAFJHOCQKVRATLM3MBGC6SI5Y4YGBXHXTRRC to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- e1d98f2125ec670dd95179e308919bd4cd09850d886830af644c03685521a8cb
- request
- aad5b49b465c69026f0b988528f7be871b9087afc0d537bf5d8cee71b2c85242
- transaction
- 2b0ec4741d8694a65c7dde750bbfb66d2c334c3d2e521d428fc7b7326032b0dbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62428
the chainentry 62428
- sealed to the entry before
- cd79ad971d0ed0b7ff2f448a2e2f0f2ee3217f4cbacf96b614f7ab023cb1bfe6
- this leaf
- 1bfb81362a5815863c1687ec42c7e9e598fd47876e3903556ccb6fa1f6134eaf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D/BlH3eE+++yzEW5j/j07mq5BhB3YBwaMFHnpATLFwicR8e5zz8c4oPgK8Z4QpRjxui5u0D3snXPGKkjXh6rBg==