why2 reasons
spend_windowspend_window_exceeded
this would take GDCT7H6BXNLK2C4AX5PTGHDMQ6H5MMHGTYQRCAAWZ5I735XDHPXJADCP 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
- 84c82e9a4b38c649cc188475132c7f8b2dccb0d63cd1de9ad8f6be63f759674f
- request
- 052bfe094ed985e0800ef05bd77b31ad91495d0724b405d821719462ee2169b5
- transaction
- 5afc41519cb3a7af2ecdf449f274496046c79bd9bc0348aeb5dcfacf6198133bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5550
the chainentry 5550
- sealed to the entry before
- fd690393144c9f6c91cbd83fbc1fecf732a259507910e64dbf4fd173ea33a911
- this leaf
- 7ccd933b03b366cce37b1264bc97705098f331ea8ff62662b03b152767b6bf75
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OMNzt9HTql5zMDLNQTaXWcuc6/KBEwom/10XfgibAuTPFH3jCJcH5OvHn3WHDZXtFGGkMaeJn5JaEJCcBX+dCw==