← previous blocknext block →recent activity
Analyzing
Block #85,166,682
14 transactions · 10 stateful · 2026-07-02 18:32:34 UTC
Parallelism
79/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,166,682 · 14 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
1w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e942750…9953
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x53c922c1…1f78
0x34b655…2a6f
3 touches
1 conflict
0x02c4bb0f…f2c8
0x34b655…2a6f
3 touches
1 conflict
0x98d58911…19f2
0x34b655…2a6f
3 touches
1 conflict
0x24227bc5…cb16
0x34b655…2a6f
2 touches
0 conflicts
0x33875aea…a440
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 0x6e9427506e…729953
Audit this contract →
← previous block·next block →recent activity