← previous blocknext block →recent activity
Analyzing
Block #82,965,721
18 transactions · 17 stateful · 2026-06-22 13:48:04 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #82,965,721 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w111w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x36a49c16…89b9
0xc8689a…ee79
8 touches
6 conflicts
0x06c59b8c…89c0
0x34b655…2a6f
8 touches
6 conflicts
0xfb859416…558c
0x34b655…2a6f
8 touches
6 conflicts
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0x41068ab1…6fa8
0x34b655…2a6f
4 touches
1 conflict
0xc3100392…575c
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
15 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity