pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,288,737
← previous block
next block →
recent activity
Analyzing
Block #90,288,737
9 transactions · 9 stateful · 2026-07-25 19:45:02 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,288,737
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
· blocks 1
#5
0x6a6512b6
#6
setData
#7
0x75c25115
#8
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x997d4606…b060
0x34b655…2a6f
4 touches
1 conflict
0xbe8aa48d…f4a2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf09d42ea…4251
0x34b655…2a6f
4 touches
1 conflict
0x1321736a…43e3
0x34b655…2a6f
4 touches
1 conflict
0x997d4606…b061
0x34b655…2a6f
4 touches
1 conflict
0x2ed336a4…72b1
0x34b655…2a6f
4 touches
1 conflict
0x2fc30b22…e3ad
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
0x997d460640…52b060
Audit this contract →
← previous block
·
next block →
recent activity