pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,250,307
← previous block
next block →
recent activity
Analyzing
Block #91,250,307
12 transactions · 12 stateful · 2026-07-29 04:37:12 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,250,307
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 2
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
bet
#8
transfer
#9
setData
#10
execOrders
· blocks 1
#7
execOrders
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98459f89…575d
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf45f2405…c8f9
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x42dfc6f5…844d
0x34b655…2a6f
4 touches
1 conflict
0x262d4253…b091
0x34b655…2a6f
2 touches
0 conflicts
0x59d06fe7…5d00
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
0x98459f8948…b6575d
Audit this contract →
← previous block
·
next block →
recent activity