← previous blocknext block →recent activity
Analyzing
Block #85,516,322
21 transactions · 18 stateful · 2026-07-04 09:21:03 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,516,322 · 21 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
1w03w04w16w07w110w114w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xea4316bc…6b4f
0x34b655…2a6f
6 touches
3 conflicts
0xc6f3c5a3…3faa
0x34b655…2a6f
5 touches
3 conflicts
0x0db8e93a…7dd1
0x34b655…2a6f
4 touches
1 conflict
0x4546ebad…b908
0x34b655…2a6f
4 touches
1 conflict
0x6637e421…af93
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x9092da13…341b
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity