pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,694,067
← previous block
next block →
recent activity
Analyzing
Block #86,694,067
10 transactions · 9 stateful · 2026-07-09 20:23:09 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,694,067
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#6
0x3f5c179b
#8
setData
#9
0xc7e3ec2c
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31ec17e3…8912
0x34b655…2a6f
4 touches
1 conflict
0x31ec17e3…8913
0x34b655…2a6f
4 touches
1 conflict
0x64800813…db9f
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9c166a56…0356
0x34b655…2a6f
4 touches
1 conflict
0xa248a5dd…4a69
0x34b655…2a6f
4 touches
1 conflict
0xdcf93b63…ae96
0x34b655…2a6f
4 touches
1 conflict
0xddbb53a9…9198
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
0x31ec17e351…8e8912
Audit this contract →
← previous block
·
next block →
recent activity