pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,385,108
← previous block
next block →
recent activity
Analyzing
Block #90,385,108
13 transactions · 12 stateful · 2026-07-26 03:57:16 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,385,108
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x50a0b275
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
0x5a5d9a99
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updatePosition
#8
execFwdPositionOps
· blocks 1
#10
forward
#11
setData
#12
execOrders
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0153faf…33ca
0x34b655…2a6f
4 touches
1 conflict
0x713ba679…f953
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x83cfbaa3…3300
0x3bd359…433a
2 touches
0 conflicts
0x997ccc40…4dfd
0x3bd359…433a
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0003
0x48cba2…b48b
2 touches
0 conflicts
0xdf7de25b…6f76
0x73e064…0148
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
0xe0153faf39…5c33ca
Audit this contract →
← previous block
·
next block →
recent activity