pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,078,909
← previous block
next block →
recent activity
Analyzing
Block #91,078,909
10 transactions · 10 stateful · 2026-07-28 14:14:53 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
#91,078,909
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
approve
#3
0x3f5c179b
#4
execFwdPositionOps
#5
0x6a68b9d4
#6
setData
#7
execOrders
· blocks 1
#9
0xc7e3ec2c
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4658f5c…b257
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1c1e591b…d93d
0x34b655…2a6f
4 touches
1 conflict
0x50afedcd…91cc
0x34b655…2a6f
4 touches
1 conflict
0x5cdbab11…77d3
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
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
0xa4658f5c4c…e0b257
Audit this contract →
← previous block
·
next block →
recent activity