← previous blocknext block →recent activity
Analyzing
Block #85,123,399
21 transactions · 17 stateful · 2026-07-02 13:44:01 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,123,399 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w18w09w110w216w017w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe47478a3…a058
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x9726104d…d160
0x34b655…2a6f
6 touches
3 conflicts
0x9c7ce94a…53b2
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x3ef0af63…992e
0x34b655…2a6f
6 touches
3 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
3 conflicts on slot 0xe47478a3e7…67a058
Audit this contract →
← previous block·next block →recent activity