← previous blocknext block →recent activity
Analyzing
Block #85,107,699
15 transactions · 13 stateful · 2026-07-02 11:58:59 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,107,699 · 15 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
1w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xaa99c369…263d
0x34b655…2a6f
6 touches
3 conflicts
0xfc9680c6…f821
0x34b655…2a6f
6 touches
3 conflicts
0x30fa662a…06e0
0x34b655…2a6f
6 touches
3 conflicts
0x4e068769…91ad
0x34b655…2a6f
4 touches
1 conflict
0x644919d7…9727
0x34b655…2a6f
4 touches
1 conflict
0x67905f6e…02a1
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity