pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,557,861
← previous block
next block →
recent activity
Analyzing
Block #95,557,861
12 transactions · 12 stateful · 2026-08-13 06:19:22 UTC
Parallelism
83
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,557,861
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x5acec890
#4
0x3f5c179b
· blocks 1
#6
execFwdPositionOps
· blocks 1
#8
0x6a7d6262
#9
transfer
· blocks 1
#11
setData
#5
batchUpdate
#7
execFwdPositionOps
#10
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0705cc6c…2c40
0x851145…3f07
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xea5af341…ad06
0x851145…3f07
4 touches
1 conflict
0xdd586d5f…56f2
0x851145…3f07
3 touches
1 conflict
0xe561281f…7569
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:
0x851145ea…9f3f07
1 conflict on slot
0x0705cc6c3d…b62c40
Audit this contract →
← previous block
·
next block →
recent activity