← previous blocknext block →recent activity
Analyzing
Block #85,110,039
17 transactions · 17 stateful · 2026-07-02 12:14:35 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,110,039 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w112w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30fa662a…06e0
0x34b655…2a6f
6 touches
3 conflicts
0x79b3209b…f766
0x34b655…2a6f
6 touches
3 conflicts
0xeebaa043…0d3c
0x34b655…2a6f
6 touches
3 conflicts
0x7324fe5d…7491
0x34b655…2a6f
6 touches
3 conflicts
0x4e068769…91ad
0x34b655…2a6f
4 touches
1 conflict
0x562f98b6…7c17
0x34b655…2a6f
4 touches
1 conflict
0x67905f6e…02a1
0x34b655…2a6f
4 touches
1 conflict
0x7372a596…bf89
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: Perpl
3 conflicts on slot 0x30fa662a9f…0906e0
Audit this contract →
← previous block·next block →recent activity