pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,026,611
← previous block
next block →
recent activity
Analyzing
Block #91,026,611
6 transactions · 4 stateful · 2026-07-28 09:51:44 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,026,611
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
setData
#5
execOrders
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bde601f…00eb
0x34b655…2a6f
4 touches
1 conflict
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0xabbaaa99…0b4a
0x34b655…2a6f
4 touches
1 conflict
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x12e8fcf0…63bb
0x34b655…2a6f
2 touches
0 conflicts
0x151a39c9…e8e2
0x34b655…2a6f
2 touches
0 conflicts
0x171352be…07ab
0x34b655…2a6f
2 touches
0 conflicts
0x2846597d…7217
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
0x2bde601f76…ee00eb
Audit this contract →
← previous block
·
next block →
recent activity