pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,618,406
← previous block
next block →
recent activity
Analyzing
Block #85,618,406
9 transactions · 8 stateful · 2026-07-04 20:40:53 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,618,406
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
0x3f5c179b
#5
0x5339c59f
#7
setData
#8
0xc7e3ec2c
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb54875c4…1a8c
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x3bf023bf…24ef
0x34b655…2a6f
2 touches
0 conflicts
0x828cefbb…7934
0x34b655…2a6f
2 touches
0 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
2 touches
0 conflicts
0x90026886…2f18
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xb54875c488…e01a8c
Audit this contract →
← previous block
·
next block →
recent activity