why1 reason
spend_windowspend_window_exceeded
this would take GDFI3DKICHBLGU6E5GNRMF7U4KAKDNXEEMKKLSNDGN5Y6M7XRFKRWD6J to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 0f9abf59d3064e4d6a279ed3330ff8a194676d5fe812deb0291a0e32c2684555
- request
- d699ab46bb5701cf700a86ff8e75bfd30ca65a2f57a4123992bd37769d891113
- transaction
- ec0eb7a0fe89391e0a5e7d14c252b3f7e0b248791193d7e220704cf133f20392computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22315
the chainentry 22315
- sealed to the entry before
- a686048cdb2f3db2ad1c3f19948669096d3a1d56e8c3d813c04b50ad14e1e19f
- this leaf
- 83cfe62a9bdd1f7fa4eece22cd88df9fda926e865e07963f24caa39a72ae25cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- da93I3Kn1GAqt7WkgFF5J8r6vPa0QI7SeLgDM+KlDzcumIC1ti16bHaZrYQzFlluG0pT3E07LGHOJp6g1I28DQ==