pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,246,234
← previous block
next block →
recent activity
Analyzing
Block #95,246,234
10 transactions · 8 stateful · 2026-08-12 04:02:21 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,246,234
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
execFwdPositionOps
· blocks 1
#4
matchOrders
#6
updateDataFeedsValuesPartial
#7
0x6a7bf0c4
#8
setData
#9
0x59558d29
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4a2636d…4d04
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x01a08f7d…dec6
0x34b655…2a6f
4 touches
1 conflict
0x67bfbc55…7b2f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x4766e371…393f
0x34b655…2a6f
2 touches
0 conflicts
0x8f203394…f2db
0x34b655…2a6f
2 touches
0 conflicts
0x8f203394…f2dc
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
0xe4a2636d85…204d04
Audit this contract →
← previous block
·
next block →
recent activity