🧵Cross-block threads

🧩Observation coverage

Observed blocks: 9 of 9 requested slots.

observed: 9, missing: 0, unavailable: 0, failed: 0, skipped: 0

Recurrence counts use observed blocks only. Missing, unavailable, failed, and skipped slots are not evidence of absent contention.

Recorded parent links

8 matched; 0 hash mismatches; 1 parent unavailable; 0 nonpreceding parent references; 0 links bypass earlier observed slots.

Direct-parent hash comparisons use supplied records only. Parents not present cannot be hash-checked. A reference bypassing another observed block prevents treating every supplied block as one ancestry path; matching links do not authenticate the source or establish canonical/finalized ancestry. Cross-block findings are recorded observations, not proof of one chain.

📦Block-by-block evidence

Summary values only. Blank CSV cells mean unavailable evidence or an unproven minimum; zero means a recorded count of zero.

Compare declared contention across observed blocks, including blocks without decoded uploads. Missing block evidence is not zero activity. Compute Units (CU) are recorded consumption, not execution time. Select a slot to inspect its full-block wave evidence. Focus a wide table with Tab and use the arrow keys to scroll.

🧵Slot-by-slot upload timeline

Contiguous byte coverage after sorting by offset. The complete upload lifecycle boundaries are not established. 148 decoded writes across 9 observed blocks cover 135,568 bytes.

148 observed chunks across 9 blocks · 135,568 observed bytes · offsets 633872-769439

Decoded chunks by transaction status: 148 successful, 0 failed, 0 unknown. Byte coverage describes decoded payloads, not verified final buffer contents.

Contiguous byte coverage after sorting by offset. Result: yes. Block-order offsets monotonic: no; 31 block-order offset inversions.

Contiguous byte coverage is determined after sorting by offset. Instruction order retains outer positions and inner indexes within each parent. Transaction order is descriptive block order only, not arrival order, scheduler order, or runtime parallelism.

Per-block causal summary

Aggregate upload totals: 1197 conflict pairs and 350760 known Compute Units. Pair percentages are not added across blocks.

Upload chunks across slots

Decoded payloads describe recorded instructions, not verified final buffer contents.

Selected slot wave evidence

Select a slot to inspect its declared full-block bounds.

Evidence links use #slot=slot-number or #chunk=sequence-index:chunk-index. Chunk indexes are zero-based within this saved report.

Underlying single-block finding

Select a slot above or in a sequence table. Internal component IDs stay inside these expandable technical details.

Select an observed slot.

🔁Prioritized recurring-contention candidates

Candidate discovery only. Recurrence does not imply redesignability. The compact view prioritizes cross-payer recurrence, decoded application state, unusual semantic footprints, multiple programs, and non-infrastructure accounts.