pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,758,229
← previous block
next block →
recent activity
Analyzing
Block #89,758,229
9 transactions · 8 stateful · 2026-07-23 23:08:14 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,758,229
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#4
0xed82b078
#5
transfer
· blocks 1
#7
setData
#8
execOrders
#3
execFwdPositionOps
#6
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22af2208…099e
0x34b655…2a6f
4 touches
1 conflict
0x76196ad0…ce0c
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x87d277ad…6f40
0x754704…b603
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
2 touches
0 conflicts
0x5164f3b2…5976
0x34b655…2a6f
2 touches
0 conflicts
0x7abf3a53…7d1b
0x34b655…2a6f
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
0x22af2208f2…fe099e
Audit this contract →
← previous block
·
next block →
recent activity