← previous blocknext block →recent activity
Analyzing
Block #86,674,981
17 transactions · 16 stateful · 2026-07-09 18:15:50 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.59
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,674,981 · 17 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
3w04w15w26w37w410w411w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
14 touches
21 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x27651ca0…581b
0x34b655…2a6f
8 touches
6 conflicts
0x554326cb…0577
0x34b655…2a6f
8 touches
6 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
8 touches
6 conflicts
0x1bde87f2…0843
0x34b655…2a6f
8 touches
6 conflicts
0xcf090a80…4536
0x34b655…2a6f
8 touches
6 conflicts
0xf726e2e2…e561
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity