pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,456,489
← previous block
next block →
recent activity
Analyzing
Block #92,456,489
11 transactions · 9 stateful · 2026-08-02 09:46:41 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,456,489
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
executeBatch
#7
execOrders
#8
0x6a6f1279
#9
setData
#10
0x59558d29
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01df0928…3427
0x34b655…2a6f
4 touches
1 conflict
0x025fef2f…9738
0x34b655…2a6f
4 touches
1 conflict
0x38a88cf1…ec2d
0x34b655…2a6f
4 touches
1 conflict
0xac2a3901…aca4
0x34b655…2a6f
4 touches
1 conflict
0x01df0928…3426
0x34b655…2a6f
4 touches
1 conflict
0x55b0fa7a…27a5
0x34b655…2a6f
4 touches
1 conflict
0xfa8497d6…3474
0x34b655…2a6f
4 touches
1 conflict
0x699ee60f…de01
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
0x01df092887…c93427
Audit this contract →
← previous block
·
next block →
recent activity