pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,169,511
← previous block
next block →
recent activity
Analyzing
Block #85,169,511
8 transactions · 8 stateful · 2026-07-02 18:51:26 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,169,511
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x39435dac
· blocks 1
#3
0x0f6795d9
#5
unlockPermanent
#6
setData
#7
0xc7e3ec2c
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fffd49d…772a
0x34b655…2a6f
4 touches
1 conflict
0x5efea426…3d66
0x34b655…2a6f
4 touches
1 conflict
0x0ec96631…b0f1
0x34b655…2a6f
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
2 touches
0 conflicts
0x198a5916…44c1
0x34b655…2a6f
2 touches
0 conflicts
0x207d2870…e720
0x34b655…2a6f
2 touches
0 conflicts
0x23253ea8…e0a4
0x34b655…2a6f
2 touches
0 conflicts
0x2380625c…1123
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
0x7fffd49db6…f8772a
Audit this contract →
← previous block
·
next block →
recent activity