← previous blocknext block →recent activity
Analyzing
Block #86,486,647
14 transactions · 13 stateful · 2026-07-08 21:14:39 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,486,647 · 14 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
4w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0x1321736a…43e3
0x34b655…2a6f
4 touches
1 conflict
0x2533f477…a43b
0x34b655…2a6f
4 touches
1 conflict
0x46346c28…1297
0x34b655…2a6f
4 touches
1 conflict
0x8b87ece6…3353
0x34b655…2a6f
4 touches
1 conflict
0x6083af24…a0df
0x34b655…2a6f
4 touches
1 conflict
0xdcae67ee…f676
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