← previous blocknext block →recent activity
Analyzing
Block #82,968,594
13 transactions · 10 stateful · 2026-06-22 14:07:16 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,968,594 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8672c4d6…675c
0x34b655…2a6f
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x588da1c1…6ae5
0x34b655…2a6f
4 touches
1 conflict
0x62db95d4…351c
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0x70cfbacf…5c46
0x34b655…2a6f
4 touches
1 conflict
0x7b2f3e6d…978f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x8672c4d6d9…2a675c
Audit this contract →
← previous block·next block →recent activity