why2 reasons
spend_windowspend_window_exceeded
this would take GD432K7OK5HGMNY6FZCT36UHNBOCSL6CCXBGYRZQB5XZBW27N7PGJ6GS 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
- 7e09e0741e4257d7eee0ed7a9d362304506f0c2cf8eadfed6c2210fe3344b57c
- request
- bdde3750bf7cca44200682b9f7b1cf5ada4d3be893d0d8a96c2b6b23e87be2d2
- transaction
- 05968a725e9c1d13899cdfeaf2498ef65a29e1141373a25cbf1c2fccf355a61fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30216
the chainentry 30216
- sealed to the entry before
- ca2ccd9129b7eb31edd55f3fd491a3dc4595cca45f2b99bc5c94c9066ab8f3c0
- this leaf
- 87ba1a1c3f96891fd584d8f5e3aa53115dfff3d862e87415a4ac1c17376f364a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0rMiAXrrMaWLMrwm235xut+I1kYHTr/iz/IBk3sU6Z3Q5ja2MizvkTUt5ema+NlRzevNQFmKnpsCvWCJMKMHDg==