pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,820,121
← previous block
next block →
recent activity
Analyzing
Block #85,820,121
7 transactions · 7 stateful · 2026-07-05 19:05:17 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,820,121
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
0x6a4aab64
#5
setData
#6
execOrders
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
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0xeb0b1d43…9559
0x34b655…2a6f
4 touches
1 conflict
0x751506a1…9e06
0x34b655…2a6f
4 touches
1 conflict
0x2d48f548…cdd5
0x34b655…2a6f
2 touches
0 conflicts
0x3beb6746…2293
0x34b655…2a6f
2 touches
0 conflicts
0x42767e6e…020d
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5317
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5318
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
0x08e8f2c94d…1ca11a
Audit this contract →
← previous block
·
next block →
recent activity