pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,185,827
← previous block
next block →
recent activity
Analyzing
Block #85,185,827
10 transactions · 10 stateful · 2026-07-02 20:40:06 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,185,827
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0x0f6795d9
#7
0x6a46cd1d
#8
setData
#9
0xc7e3ec2c
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd16df6cd…5532
0x40c49f…2af0
4 touches
1 conflict
0xf5310ef7…485a
0x40c49f…2af0
4 touches
1 conflict
0xfb7870c9…42de
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x0226e8d9…5ff5
0x40c49f…2af0
3 touches
1 conflict
0x1151f694…3240
0x40c49f…2af0
3 touches
1 conflict
0x2f74f175…9284
0x69df8a…6292
2 touches
0 conflicts
0x2f74f175…9285
0x69df8a…6292
2 touches
0 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:
0x40c49f17…d22af0
1 conflict on slot
0xd16df6cdbe…065532
Audit this contract →
← previous block
·
next block →
recent activity