← previous blocknext block →recent activity
Analyzing
Block #82,966,626
44 transactions · 35 stateful · 2026-06-22 13:54:07 UTC
Parallelism
66/100
Blocked
69%
Avg conflicts / tx
2.75
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #82,966,626 · 44 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w18w011w112w013w114w215w316w417w518w619w721w822w923w1025w128w131w236w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
22 touches
55 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xd5a3236b…6b26
0x34b655…2a6f
14 touches
21 conflicts
0x36a49c16…89b9
0xc8689a…ee79
12 touches
15 conflicts
0x326a02b5…8dad
0x34b655…2a6f
12 touches
15 conflicts
0xa1571d54…ae41
0x34b655…2a6f
12 touches
15 conflicts
0x2efd014a…3e8c
0x34b655…2a6f
10 touches
12 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
55 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity