← previous blocknext block →recent activity
Analyzing
Block #85,168,364
15 transactions · 13 stateful · 2026-07-02 18:43:47 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,168,364 · 15 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
6w07w111w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x4c9a43f9…6f14
0x188d58…ea8e
2 touches
0 conflicts
0x4c9a43f9…6f15
0x188d58…ea8e
2 touches
0 conflicts
0x17606ba6…1b6e
0x754704…b603
2 touches
0 conflicts
0x5d5b27f4…e39c
0x754704…b603
2 touches
0 conflicts
0x00000000…0003
0x942644…91ab
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 0x6bdb9869c7…427558
Audit this contract →
← previous block·next block →recent activity