← previous blocknext block →recent activity
Analyzing
Block #96,795,478
12 transactions · 10 stateful · 2026-08-17 14:06:02 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,795,478 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w18w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe16c59e1…e3aa
0x8964d7…10f8
4 touches
1 conflict
0x6854b21d…077b
0x8964d7…10f8
4 touches
1 conflict
0x6854b21d…077e
0x8964d7…10f8
4 touches
1 conflict
0x6854b21d…077f
0x8964d7…10f8
4 touches
1 conflict
0x6854b21d…0781
0x8964d7…10f8
4 touches
1 conflict
0xe16c59e1…e3a7
0x8964d7…10f8
4 touches
1 conflict
0xe16c59e1…e3a8
0x8964d7…10f8
4 touches
1 conflict
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x8964d7c9…5b10f8
1 conflict on slot 0xe16c59e108…f4e3aa
Audit this contract →
← previous block·next block →recent activity