← previous blocknext block →recent activity
Analyzing
Block #82,293,382
13 transactions · 12 stateful · 2026-06-19 10:56:37 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,293,382 · 13 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
2w03w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x511ecf07…8ed0
0x34b655…2a6f
4 touches
1 conflict
0x60c7217a…8c94
0x34b655…2a6f
4 touches
1 conflict
0x7b3f8378…b37d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xcfc8024c…8261
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
1 conflict on slot 0x511ecf073e…d98ed0
Audit this contract →
← previous block·next block →recent activity