← previous blocknext block →recent activity
Analyzing
Block #82,966,354
11 transactions · 9 stateful · 2026-06-22 13:52:18 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,966,354 · 11 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
1w05w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe496e2a…ea17
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x7e8ebc95…aded
0x34b655…2a6f
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x3e242d19…6f58
0x34b655…2a6f
2 touches
0 conflicts
0x67c705da…e7d6
0x34b655…2a6f
2 touches
0 conflicts
0x6cb00991…3f9e
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 0xfe496e2ab7…d8ea17
Audit this contract →
← previous block·next block →recent activity