pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,136,852
← previous block
next block →
recent activity
Analyzing
Block #91,136,852
9 transactions · 8 stateful · 2026-07-28 19:06:25 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,136,852
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execOrders
#5
0x6a68fe28
#6
setData
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc351d6d…256b
0x34b655…2a6f
4 touches
1 conflict
0x0f3152e8…f181
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x053ec9be…ccbf
0x34b655…2a6f
2 touches
0 conflicts
0x08954241…4690
0x34b655…2a6f
2 touches
0 conflicts
0x09a168cc…dcc0
0x34b655…2a6f
2 touches
0 conflicts
0x1bc2d5a2…d6ac
0x34b655…2a6f
2 touches
0 conflicts
0x259ed0cc…bef9
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
0xcc351d6dd2…b1256b
Audit this contract →
← previous block
·
next block →
recent activity