pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,845,733
← previous block
next block →
recent activity
Analyzing
Block #85,845,733
9 transactions · 9 stateful · 2026-07-05 21:55:54 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,845,733
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0xed82b078
#4
0xed82b078
#5
setData
#8
0xc7e3ec2c
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9966da31…0d0f
0x34b655…2a6f
4 touches
1 conflict
0x62717024…ac25
0x34b655…2a6f
4 touches
1 conflict
0x141c490e…8343
0x34b655…2a6f
4 touches
1 conflict
0xa4658f5c…b257
0x34b655…2a6f
4 touches
1 conflict
0xb1939b09…99dd
0x34b655…2a6f
4 touches
1 conflict
0x27c3d357…3161
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
0x9966da3102…c80d0f
Audit this contract →
← previous block
·
next block →
recent activity