← previous blocknext block →recent activity
Analyzing
Block #85,139,191
19 transactions · 18 stateful · 2026-07-02 15:29:32 UTC
Parallelism
68/100
Blocked
28%
Avg conflicts / tx
0.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,139,191 · 19 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
3w04w15w211w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebda062f…e87a
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x3230277c…ef39
0xc8689a…ee79
4 touches
1 conflict
0x0e5f2a94…4732
0x34b655…2a6f
4 touches
1 conflict
0x25e3730b…24a9
0x34b655…2a6f
4 touches
1 conflict
0x37421b44…45b5
0x34b655…2a6f
4 touches
1 conflict
0x3eb30213…3f2a
0x34b655…2a6f
4 touches
1 conflict
0x43e2eda1…396f
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
3 conflicts on slot 0xebda062ff9…83e87a
Audit this contract →
← previous block·next block →recent activity