← previous blocknext block →recent activity
Analyzing
Block #85,276,659
20 transactions · 17 stateful · 2026-07-03 06:45:06 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,276,659 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w29w310w411w513w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xd597209e…9800
0x34b655…2a6f
6 touches
3 conflicts
0x9495bffc…46e6
0x34b655…2a6f
6 touches
3 conflicts
0xff68cfaf…2cca
0x34b655…2a6f
6 touches
3 conflicts
0x3230277c…ef39
0xc8689a…ee79
6 touches
3 conflicts
0x8f9b6254…f564
0x34b655…2a6f
4 touches
1 conflict
0x98a31d7b…319d
0x34b655…2a6f
4 touches
1 conflict
0xd423a934…6dea
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity