← previous blocknext block →recent activity
Analyzing
Block #85,138,011
16 transactions · 14 stateful · 2026-07-02 15:21:39 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,138,011 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w28w312w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe47478a3…a058
0x34b655…2a6f
6 touches
3 conflicts
0xea4b86ec…900f
0x34b655…2a6f
6 touches
3 conflicts
0xa749be9d…5226
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xc3c7cf34…43da
0x34b655…2a6f
6 touches
3 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
4 touches
1 conflict
0x7a811ab6…235a
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
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
3 conflicts on slot 0xe47478a3e7…67a058
Audit this contract →
← previous block·next block →recent activity