← previous blocknext block →recent activity
Analyzing
Block #83,632,665
20 transactions · 20 stateful · 2026-06-25 16:04:10 UTC
Parallelism
55/100
Blocked
50%
Avg conflicts / tx
2.3
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,632,665 · 20 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
2w03w14w25w36w47w58w69w717w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x619f5683…5bd4
0x34b655…2a6f
18 touches
36 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
14 touches
21 conflicts
0x5396d712…a139
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
14 touches
21 conflicts
0xcff90c3c…0456
0x34b655…2a6f
10 touches
10 conflicts
0xa4492001…ef07
0x34b655…2a6f
8 touches
6 conflicts
0x0be10f9e…620c
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x619f5683ba…f75bd4
Audit this contract →
← previous block·next block →recent activity