why2 reasons
spend_windowspend_window_exceeded
this would take GCH4QHAU4PC654K5KFHRJGCNU4A5EFH62O2BGTL4YC2VIYS4TREM3QDO 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
- 2f1de55bc0870ad5b21c83b1164b3d21ff6cd6adf4597ec8f8ae7b1d7a8fba9a
- request
- 04ede21ac8632adbbcf8246939cab66a53412e9769e0fdb2b165dbf89cf1163c
- transaction
- e39ad167cffa2f824cc7390faf247e44e1233ee92fde981e321ed5cd195d4cbbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4987
the chainentry 4987
- sealed to the entry before
- 0bedf67d02bd0806af2112db5de94957ba8bfb75496872602162e613aba991f0
- this leaf
- a9c94b9aaca63baed6ff180e8e4e5fd4361cead42f7dc1eae9fd4dd2006bc6b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D4xK1KHGQFaq6FLf+YdfJACiLN5uJQp8ykrjENpEpXuZjIsfYdXvSEoGsWUk1G0Mc0RC8+fWncxXpYMlYC3oBA==