pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,209,283
← previous block
next block →
recent activity
Analyzing
Block #90,209,283
11 transactions · 10 stateful · 2026-07-25 13:03:55 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,209,283
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x6a64b4b3
#3
0x15ea9545
#4
updateDataFeedsValuesPartial
#5
0x57368ddf
#6
execFwdPositionOps
#7
execFwdPositionOps
· blocks 1
#9
setData
#10
0xc7e3ec2c
#8
execFwdPositionOps
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
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7b157e63…17aa
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0002
0x48cba2…b48b
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x002a0f9e…b33b
0xea1b8e…c5ec
2 touches
0 conflicts
0x1728ed63…499c
0xea1b8e…c5ec
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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity