pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,210,438
← previous block
next block →
recent activity
Analyzing
Block #91,210,438
10 transactions · 9 stateful · 2026-07-29 01:16:34 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,210,438
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#6
0x3f5c179b
#8
0x6a6954ea
#9
setData
#5
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcef70a96…db44
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xcbfeb997…6e11
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
0x34b655…2a6f
5 touches
3 conflicts
0x0422e0ce…38ba
0x34b655…2a6f
4 touches
1 conflict
0x34933aba…06e5
0x34b655…2a6f
4 touches
1 conflict
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
0xcef70a965c…28db44
Audit this contract →
← previous block
·
next block →
recent activity