← previous blocknext block →recent activity
Analyzing
Block #83,028,156
13 transactions · 12 stateful · 2026-06-22 20:45:50 UTC
Parallelism
39/100
Blocked
58%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,028,156 · 13 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd99b3b64…1c95
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x98d58911…19f2
0x34b655…2a6f
10 touches
14 conflicts
0x36a49c16…89b9
0xc8689a…ee79
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0x926eb04e…d1cd
0x34b655…2a6f
10 touches
10 conflicts
0xf7e84d35…ad5c
0x34b655…2a6f
10 touches
10 conflicts
0xffb8950c…23c6
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xd99b3b6441…7a1c95
Audit this contract →
← previous block·next block →recent activity