pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,125,531
← previous block
next block →
recent activity
Analyzing
Block #95,125,531
12 transactions · 8 stateful · 2026-08-11 17:51:14 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,125,531
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
· blocks 1
#3
execOrders
#4
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
0x3f5c179b
#9
0x6a7b618a
#10
setData
#11
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x20d1947c…4807
0x34b655…2a6f
4 touches
1 conflict
0x1062ca99…dc10
0x34b655…2a6f
2 touches
0 conflicts
0x11401e68…c822
0x34b655…2a6f
2 touches
0 conflicts
0x23153440…0007
0x34b655…2a6f
2 touches
0 conflicts
0x4bc1abab…5874
0x34b655…2a6f
2 touches
0 conflicts
0x50e54461…beba
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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity