← previous blocknext block →recent activity
Analyzing
Block #80,635,035
67 transactions · 15 stateful · 2026-06-11 18:43:07 UTC
Parallelism
91/100
Blocked
40%
Avg conflicts / tx
0.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,635,035 · 67 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w128w241w356w164w465w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
8 touches
6 conflicts
0x00ea5f69…5cdf
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x182f9344…d013
0x34b655…2a6f
4 touches
1 conflict
0x1f9b09b8…17d9
0x34b655…2a6f
4 touches
1 conflict
0x3732c6c9…ded6
0x34b655…2a6f
4 touches
1 conflict
0x38c80f15…d8f2
0x34b655…2a6f
4 touches
1 conflict
0x428ba454…0d9c
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
6 conflicts on slot 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity