← previous blocknext block →recent activity
Analyzing
Block #85,837,352
20 transactions · 18 stateful · 2026-07-05 21:00:01 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
1.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,837,352 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w111w212w314w115w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
10 touches
10 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x385fcdf5…cf23
0x34b655…2a6f
6 touches
3 conflicts
0x4d8a8821…df85
0x34b655…2a6f
6 touches
3 conflicts
0x6f58168d…ea24
0x34b655…2a6f
6 touches
3 conflicts
0x7506443a…4820
0x34b655…2a6f
6 touches
3 conflicts
0x7e4b5149…c444
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity