← previous blocknext block →recent activity
Analyzing
Block #85,135,658
13 transactions · 11 stateful · 2026-07-02 15:05:56 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,135,658 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea4b86ec…900f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0x11431f9d…42c5
0x34b655…2a6f
4 touches
1 conflict
0x0b2a838b…287c
0x34b655…2a6f
2 touches
0 conflicts
0x1e7e4246…4872
0x34b655…2a6f
2 touches
0 conflicts
0x4caf91f9…8ab5
0x34b655…2a6f
2 touches
0 conflicts
0x6bdb9869…7558
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xea4b86ec74…1a900f
Audit this contract →
← previous block·next block →recent activity