why2 reasons
spend_windowspend_window_exceeded
this would take GD5GLUQRTPHFBOMOC5CYS6PBMRTO44XHI7Y7ZW6K724MUT6T7UYHN3W7 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
- dbdd8946a3c8390d3e4ae54e79bb54791a9d4bfe136be17133c7d28ac2c527d8
- request
- 1fbdf3a5738db5a70b4e185186066ecd403f9f058bfc4569a53ad366417fb7ab
- transaction
- b05d274304e690929cea2a4dcd1d4c0859e8300f8de529b91cc4a18fd391e0fbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9397
the chainentry 9397
- sealed to the entry before
- 0e762b2879bdbc162c71ed141d6dd2a06791eaf436584452cbb105561be53ad2
- this leaf
- eb7b9e502a6218015e31f8f18e76406c5dff4d3d04e3ee15fcc0133ee9c4caf0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Gwh8QsIG5N3thnBPDPSpPyanx1TlKkU/sgWX9Ik8at4uS6AGEZw162fEepkpdh9OwtFNimqym1FyqhWNIAK9CQ==