pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,431,397
← previous block
next block →
recent activity
Analyzing
Block #91,431,397
10 transactions · 8 stateful · 2026-07-29 19:50:29 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,431,397
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a6a59fd
#2
0x6a6a59fd
#3
supply
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 2
#7
setData
#9
0x59558d29
#6
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e6b8ec7…2197
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x177f8108…ff11
0x34b655…2a6f
4 touches
1 conflict
0x013d2e36…9c3e
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x47729858…a47c
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0036
0x35a73b…6042
2 touches
0 conflicts
0x3da2634e…f95f
0x35a73b…6042
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
3 conflicts on slot
0x6e6b8ec76e…cb2197
Audit this contract →
← previous block
·
next block →
recent activity