pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,396,105
← previous block
next block →
recent activity
Analyzing
Block #91,396,105
9 transactions · 9 stateful · 2026-07-29 16:51:40 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,396,105
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x6a6a3014
#6
setData
#7
0x59558d29
#8
0xc7e3ec2c
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74dae4f2…f2d8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x07d110f6…e378
0x34b655…2a6f
2 touches
0 conflicts
0x07d110f6…e379
0x34b655…2a6f
2 touches
0 conflicts
0x08ef3bd6…e154
0x34b655…2a6f
2 touches
0 conflicts
0x106e4432…b0a4
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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
0x74dae4f22f…6ef2d8
Audit this contract →
← previous block
·
next block →
recent activity