why2 reasons
spend_windowspend_window_exceeded
this would take GBGKM6A5ME4FQITIYCB4GKL3JITMT22C25A3D5RHXVIGYAL7FYAIC6DC to 70 over the last 60000ms, above the 12 window cap, with 0 already spent
mandateamount_exceeds_cap
op 0 pays 70.0000000, cap is 40
what it was decided fromfingerprints
- rule compiled from it
- 96023f515108ffa711f9de90623c67267fa7ba967d74525a953867d4d5d1abe9
- request
- a477eb7f7a64f6597d83407419c1483a6792554bb423c95143e7eb80ea2fc3e3
- transaction
- 0ae38cdff80b5c626254264140ee4819eff781f94ddcec05f7fd0c6e77b2c84dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64443
the chainentry 64443
- sealed to the entry before
- 1aad6b9b0abbb04b562eaddc4fc924d78a2ad485dca943420ae49236522f8ae3
- this leaf
- 3d03a7cd2b855ed94f2a88e11eb146917596533a117bb3f25640277dd60c3831
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DE13lxhEdAgDNS2hvFB7mQa5x6TQ5OfCI9XC1QQgqlYKEy/CTfm/YSxT+2Sw2MHGNA1G9ISqQEecug6/Q08FCg==