pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,607,792
← previous block
next block →
recent activity
Analyzing
Block #91,607,792
14 transactions · 9 stateful · 2026-07-30 10:37:54 UTC
Parallelism
86
/100
Blocked
11
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,607,792
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0x0c7abd22
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#7
0x3f5c179b
#8
execOrders
#9
execOrders
#10
execOrders
#11
setData
#12
withdraw
#13
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x032129e7…0add
0x34b655…2a6f
2 touches
0 conflicts
0x3ab787fc…6a13
0x34b655…2a6f
2 touches
0 conflicts
0x691e77f9…49ed
0x34b655…2a6f
2 touches
0 conflicts
0x6cd18858…a7be
0x34b655…2a6f
2 touches
0 conflicts
0x91cdfdeb…7feb
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
0x91b0f8edc5…b76bd7
Audit this contract →
← previous block
·
next block →
recent activity