← previous blocknext block →recent activity
Analyzing
Block #86,836,871
25 transactions · 20 stateful · 2026-07-10 12:17:19 UTC
Parallelism
68/100
Blocked
65%
Avg conflicts / tx
1.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,836,871 · 25 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
1w02w13w24w05w16w27w38w39w210w311w413w514w623w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x8d888c90…5479
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x8060f612…9559
0x34b655…2a6f
8 touches
6 conflicts
0x8656a13f…f95e
0x34b655…2a6f
8 touches
6 conflicts
0xb081c1ec…4b7b
0xd32edf…ff58
7 touches
6 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity