pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,343,132
← previous block
next block →
recent activity
Analyzing
Block #88,343,132
10 transactions · 10 stateful · 2026-07-17 12:11:32 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
#88,343,132
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
execFwdPositionOps
#3
updateDataFeedsValuesPartial
#4
0x3b073534
#5
execFwdPositionOps
· blocks 1
#7
0x6a5a1c6b
#8
setData
#9
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffcb5f20…df5a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0eec24ec…835b
0x34b655…2a6f
2 touches
0 conflicts
0x1533cfc9…c4f9
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x1df736b6…61c3
0x34b655…2a6f
2 touches
0 conflicts
0x3a565e61…7dbb
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
0xffcb5f205c…83df5a
Audit this contract →
← previous block
·
next block →
recent activity