why1 reason
spend_windowspend_window_exceeded
this would take GC5YADKPVGL4YOAYDBRILZMZCDZJMKXAHG7HLX5MVPTJ4TROL2PWG2HX to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 30a70488f1c39007a49a41e67937cbba6741ee1dfa33ac5545ed47726513720a
- request
- f2946c4240f3d416a2e364cb956e293ea852a63f02d82c2b7d1b0aee99d6eb18
- transaction
- d54c428598cc1b3885da30ae695f3c14bf51047cc327380ec92ac4310edcefafcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52385
the chainentry 52385
- sealed to the entry before
- a53a70733df11af45b16a6ef427e4fdd233eafdde1c357e6b7efb0b23c5691ed
- this leaf
- 9dcecf15a5b8ba289acc0e5d8ddda7d30f920fba7bc6f968852580f02292f505
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +15JuN/bGzi01EjXs37KU8TWHE98RJlUCHlVeRmLYRT5x3spQMIAJfa9df7Z13kGQkJDt9gQDWBJPRFaphm1CQ==