← previous blocknext block →recent activity
Analyzing
Block #82,966,082
30 transactions · 25 stateful · 2026-06-22 13:50:29 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
1.1
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #82,966,082 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w416w518w122w624w726w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0x36a49c16…89b9
0xc8689a…ee79
10 touches
10 conflicts
0xfb859416…558c
0x34b655…2a6f
10 touches
10 conflicts
0xf324b405…ca30
0x34b655…2a6f
10 touches
10 conflicts
0x08913286…f0df
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xd9a92b6a…01dc
0x34b655…2a6f
8 touches
6 conflicts
0x9b2427b9…2a41
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity