pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,964,290
← previous block
next block →
recent activity
Analyzing
Block #86,964,290
10 transactions · 9 stateful · 2026-07-11 02:29:03 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,964,290
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5bf9264c
#3
0x5bf9264c
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x0f6795d9
· blocks 1
#9
setData
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb104db11…2208
0x34b655…2a6f
4 touches
1 conflict
0xb652c396…b8fa
0x34b655…2a6f
4 touches
1 conflict
0xce3de73c…ae35
0x34b655…2a6f
4 touches
1 conflict
0xce3de73c…ae36
0x34b655…2a6f
4 touches
1 conflict
0xd886864d…52e8
0x34b655…2a6f
4 touches
1 conflict
0xfee72f1e…0aee
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
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
1 conflict on slot
0xb104db11bd…402208
Audit this contract →
← previous block
·
next block →
recent activity