← previous blocknext block →recent activity
Analyzing
Block #88,082,554
12 transactions · 12 stateful · 2026-07-16 07:08:05 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,082,554 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310afe2c…83e1
0x34b655…2a6f
6 touches
3 conflicts
0xe7382927…0ea6
0x34b655…2a6f
4 touches
1 conflict
0x7c6cfc14…9957
0x34b655…2a6f
4 touches
1 conflict
0xb550abea…2729
0x34b655…2a6f
4 touches
1 conflict
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x27b9caf2…c102
0x34b655…2a6f
2 touches
0 conflicts
0x2bcdd4a1…3d3a
0x34b655…2a6f
2 touches
0 conflicts
0x6278b1b2…ba7b
0x34b655…2a6f
2 touches
0 conflicts
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: Perpl
3 conflicts on slot 0x310afe2cd5…d683e1
Audit this contract →
← previous block·next block →recent activity