← previous blocknext block →recent activity
Analyzing
Block #80,826,385
23 transactions · 13 stateful · 2026-06-12 15:58:53 UTC
Parallelism
87/100
Blocked
31%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,826,385 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w19w113w015w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x576801fc…f80b
0x34b655…2a6f
6 touches
3 conflicts
0x6dda71b6…7aa7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2ff3d3e6…71ed
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x2660e7da…5f37
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 0x576801fcf9…a5f80b
Audit this contract →
← previous block·next block →recent activity