← previous blocknext block →recent activity
Analyzing
Block #85,570,452
19 transactions · 14 stateful · 2026-07-04 15:21:31 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,570,452 · 19 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
1w02w16w07w110w212w015w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x2267f8c4…a571
0x34b655…2a6f
4 touches
1 conflict
0x23253ea8…e0a4
0x34b655…2a6f
4 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0x3b8a8067…1c70
0x34b655…2a6f
4 touches
1 conflict
0x425f516b…80fd
0x34b655…2a6f
4 touches
1 conflict
0x50887223…db7f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity