why1 reason
spend_windowspend_window_exceeded
this would take GBTIDYR23S2R6FPA5OAUYSE4R5EBU4EVJTVTQPHDJL3HVWJQKBM27NXT to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- ea58bedf2b487c0c4c54c3384d739a0a4ed2117bc34920c91ae613df83cf4c3d
- request
- 64ca4d8aeb62bb546b7a83748c0577a800ce63e03bde6661e4c1ad7ed1458cee
- transaction
- 790b9773c378bc6162bff2c985e309c9062653c52b070eb8f983511f45703edecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72902
the chainentry 72902
- sealed to the entry before
- 9e358cf6ff6bd68918031bcae66e6bc5e859d182e9684703d181a20e423228d2
- this leaf
- d83d514422fcb1d4a704729858ffe181f81eea4720130b56eed5c34e536bd9e7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4bIj7eG+NfHR+INz/wF26L805TL+2uz5FVvG4w997d3NMqhLR79pj14J9Sp+/hucfJRilooWcdGpSLovpkfUBA==