← previous blocknext block →recent activity
Analyzing
Block #85,630,501
10 transactions · 9 stateful · 2026-07-04 22:01:23 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,630,501 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadadad23…f057
0x34b655…2a6f
8 touches
6 conflicts
0xdc746738…0698
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x316d90ef…fe4a
0x34b655…2a6f
5 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x061b18ea…0358
0x34b655…2a6f
4 touches
1 conflict
0x2b350b0e…67de
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
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
6 conflicts on slot 0xadadad23ab…63f057
Audit this contract →
← previous block·next block →recent activity