pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,692,979
← previous block
next block →
recent activity
Analyzing
Block #90,692,979
10 transactions · 9 stateful · 2026-07-27 05:52:23 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,692,979
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#2
execFwdPositionOps
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x60c06040
#6
batchUpdate
#8
setData
#9
0x32366535
#5
execFwdPositionOps
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
5
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x883024bf…6a12
0x34b655…2a6f
4 touches
1 conflict
0x958294fe…2c10
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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
0x0dd3d3cd18…c87281
Audit this contract →
← previous block
·
next block →
recent activity