← previous blocknext block →recent activity
Analyzing
Block #86,083,950
21 transactions · 19 stateful · 2026-07-07 00:24:55 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,083,950 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w07w09w110w115w116w217w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xb1939b09…99dd
0x34b655…2a6f
8 touches
6 conflicts
0xa7396f51…7f2f
0x34b655…2a6f
6 touches
3 conflicts
0x187291ec…a543
0x34b655…2a6f
4 touches
1 conflict
0x2888c22f…0a6f
0x34b655…2a6f
4 touches
1 conflict
0x4a31a1e5…f90a
0x34b655…2a6f
4 touches
1 conflict
0x547feec8…29b6
0x34b655…2a6f
4 touches
1 conflict
0x62717024…ac25
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