pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,162,764
← previous block
next block →
recent activity
Analyzing
Block #92,162,764
10 transactions · 9 stateful · 2026-08-01 09:09:33 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,162,764
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
setData
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
execOrders
· blocks 1
#8
0xc7e3ec2c
#9
0xc7e3ec2c
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01a08f7d…dec6
0x34b655…2a6f
4 touches
1 conflict
0xd2274a53…9d6a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1eb410fd…591d
0x34b655…2a6f
4 touches
1 conflict
0x50260e8c…4789
0x34b655…2a6f
4 touches
1 conflict
0xb83387da…d672
0x34b655…2a6f
4 touches
1 conflict
0xc1a31e89…f9b1
0x34b655…2a6f
4 touches
1 conflict
0xc6830bf0…6589
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
1 conflict on slot
0x01a08f7dea…2ddec6
Audit this contract →
← previous block
·
next block →
recent activity