← previous blocknext block →recent activity
Analyzing
Block #82,965,136
31 transactions · 24 stateful · 2026-06-22 13:44:08 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.26
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #82,965,136 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w113w014w115w216w317w418w519w623w724w228w829w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0xd5a3236b…6b26
0x34b655…2a6f
10 touches
10 conflicts
0xfb859416…558c
0x34b655…2a6f
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0x36a49c16…89b9
0xc8689a…ee79
8 touches
6 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641e
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
21 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity